False Positive Remediation

Version 0.16.0 introduced regular testing for false-positive-prone targets, as well as their automatic exclusion from searches. This provided a significant boost to the project's average accuracy, but as sites drift over time, the effective scope shrinks.

Users wanting to contribute to the project can either submit new targets, or, now, they can referencethis file for the list of known-problematic sites and work on correcting their entry.

Contribution Guide

When opening your pull request, please search for any open issues relating to the false positive status of that site. If one exists, please link it by using theFixes: keyword in your request. For instanceFixes: #0000.Please do not useFixes: #2547 for individual sites - if a ticket doesn't exist for your site, it can be omitted. Additionally, for tickets with multiple sites, do not useFixes unless fixingall listed sites.

Sites included in the above file are excluded by default from searches, but theywill be hit when referenced directly via the--site option. Keep this in mind for testing.

Users contributing either corrections or new sites are required to first validate their contribution. Commits that introduce new false positives or false negativeswill not be merged, as they dirty the manifest. When ran with--local, the application will reference your local manifest rather than upstream (useful for local testing and development).