Reporting a problem with a report
To help us reproduce an issue, include the extension name and version, the store URL or file type, the finding or score you believe is wrong, and the evidence shown in the report. Do not send a full package unless requested; a link to the public store listing is usually enough.
Responsible disclosure
If you believe the site or API has a security issue, contact us before publishing details. Include steps to reproduce and the impact you observed. Please do not access other users' data, disrupt the service or run destructive tests.
What we cannot do
We cannot verify that an extension is safe, remove store listings, or provide legal or security certification. For suspected malware, report the extension to the relevant browser store and, where appropriate, to the relevant authorities.
Corrections to articles
Content pages are reviewed periodically. If a technical statement is inaccurate or out of date, send the page URL and the correction with a supporting source. Reviewed corrections update the "last reviewed" date on the page.
Privacy
Do not include passwords, authentication tokens or personal data in an email. Our handling of site data is described in the privacy policy.