GitHub Security Policy and Dependency Update Procedure
Write a security policy and dependency routine (defensive).
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a security policy and dependency update procedure for [PROJECT], as a defensive policy for software my team maintains. Supported versions: [SUPPORTED_VERSIONS]. How we want to receive vulnerability reports: [REPORTING_ROUTE]. Maintainers who respond: [MAINTAINERS]. Dependency tools in use (Dependabot, lock files, scanners): [TOOLS]. SECURITY.md content: supported versions, how to report privately, what to include, realistic response times a small team can meet, the disclosure approach and a thank-you. Include a message template acknowledging a report. Do not include exploit details. Dependency procedure: how updates are proposed, who reviews, how major updates are tested, how critical security updates are expedited, how to deal with abandoned packages, and how licence changes are reviewed. Add a one-page checklist for a leaked secret (revoke, rotate, review history, notify, clean up), a 30-minute monthly routine, and a metric: the number of open security alerts older than 30 days. Mark feature names and settings [VERIFY]. Write the policy in plain language a volunteer maintainer can follow, and say which parts to drop if the project has only one maintainer.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.