This is the default security policy for the Scrape.do organisation's public
repositories. A repository with its own SECURITY.md is covered by that file
instead; it may name additional scope, versions and timelines.
Please do not report security vulnerabilities through public GitHub issues, discussions or pull requests.
Report them privately, in either of these ways:
- GitHub private vulnerability reporting: on the repository page, open Security → Report a vulnerability (on repositories that offer it). This creates a private advisory draft visible only to you and the maintainers.
- Email: support@scrape.do. PGP is available on request.
Include what the issue is, the steps or a proof of concept to reproduce it, the affected repository and version, and what you think the impact is. Never include a real API token or other credential in the report.
You will get an acknowledgement within 3 business days and a triage and severity assessment within 7 business days. We will keep you informed while we investigate and will credit you in the advisory when the fix is published, unless you prefer otherwise.
In scope: the code published in the organisation's repositories, their build
and release pipelines, and the packages they publish (Go modules, npm and PyPI
packages, release binaries, and the Homebrew formulae and casks and the Scoop
manifests the organisation publishes, for example in
scrape-do/homebrew-tap and scrape-do/scoop-bucket).
Out of scope: the Scrape.do service itself (the API, the dashboard and scrape.do websites), which is reported to support@scrape.do directly rather than through GitHub; denial-of-service findings that only consume the reporter's own credits; and findings that require an already-compromised machine.
Unless a repository says otherwise, security fixes ship in a new release of the latest minor version; older minors are not patched. Upgrade to the latest release to receive fixes.