Skip to content

Submit app comparison #122

@galeksandrp

Description

@galeksandrp
Submit app comparison (+sources) Generators comparison (+sources) Domain enumerators

Submit app comparison

Backend Frontend Prod License Dependencies GitHub caps
galeksandrp/https-everywhere@webhook galeksandrp/httpse MIT Travis GitHub Docker (galeksandrp/https-everywhere@docker-httpse)
galeksandrp/https-everywhere@webhook-2 galeksandrp/https-everywhere@gh-pages MIT Travis GitHub Docker (galeksandrp/https-everywhere@docker-httpse) public_repo
galeksandrp/https-everywhere@webhook-client galeksandrp/galeksandrp.github.io@master MIT Travis GitHub Docker (galeksandrp/https-everywhere@docker-httpse) public_repo email

Generators support

Author/Link @Foorack EFForg/https-everywhere#6912 (comment) gloomy-ghost/ew@master galeksandrp/https-everywhere@check-sublist3r @pgerber #7706 Foorack/httpse-ruleset-generator@master
galeksandrp/httpse ✔️ ✔️ ✔️
galeksandrp/https-everywhere@gh-pages
galeksandrp/galeksandrp.github.io@master

✔️ not deployed to prod
✅ deployed to prod

https://github.com/galeksandrp/httpse/issues/new
  • No progress shown, but you can just wait when your PR will be arrived or see Travis log for specified *-auto branch in repo below.
  • Incoming PRs will have mine as author. (fix can produce issues since github limit unanteficated requests to 60 per hour)
  • Use github-email for discovering email.
  • Single ruleset can't be PRed once. (branch will be rebased if existing branch have old test scripts)
  • If ruleset is already present in HTTPSE and have different filename than lowercase.domain.xml PR will be created, but PR's Travis will fail.
  • Issue number not passed to PR, so issue can't be automatically closed.
  • Even empty ruleset will be PRed.
  • ~~~Scan limit is 10m.~~~ Now 50m.
  • Use shallow clone for speedup.
  • Mention issue author in PR.
  • Automatically comment && close issue when HSTS or no rules found.
https://galeksandrp.github.io/https-everywhere/
Open PRs
  • Check empty comment
  • Rescan rulesets
  • Rescan rulesets for mixed content

My mixed content position

Achived copy of this post in my repository: #122 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions