scrape-do-python is currently pre-1.0.

Security fixes are applied to the latest minor version on main

Once 1.0 ships, this table will be updated to reflect the standard latest minor + previous minor support window.

Please do not open public GitHub issues for security vulnerabilities.

Use one of these private channels instead:

1. Preferred: GitHub Security Advisories — opens a private discussion only the maintainer can see.
2. Fallback: email svdc1mail@gmail.com with the subject line [scrape-do-python security].

When reporting, please include:

• A clear description of the vulnerability and its impact.
• Steps to reproduce, or a minimal proof-of-concept.
• The affected version(s).
• Any suggested mitigation, if you have one.

The maintainer will acknowledge your report within 7 days on a best-effort basis. If the vulnerability is confirmed, a fix will be prepared on a private branch and disclosed coordinated with a release. Reporters who wish to be credited will be acknowledged in the release notes.