You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agentic AI has drastically changed the security landscape by making vulnerabilities much easier to discover and exploit. This puts a lot of pressure on maintainers to stay vigilant and respond quickly to new threats by updating and patching their packages. It also makes good security hygiene more important than ever.
We could add a section to the guide with recommendations that help maintainers be proactive in two ways:
Preventing common vulnerabilities: code analysis, vulnerability scanners, etc.
Limiting exposure and making it easier to respond to a threat: best practices, dependency management, etc.
This issue comes from our first Docs & Infrastructure Sprint call on Nov 9th.
Hi @flpm and @lwasser, I'd like to contribute to this section. Could I start with an outline for dependency security and a worked Python dependency-auditing example? I'd cover checking for known vulnerabilities, interpreting findings and documenting remediation, with links to existing guidance. I can coordinate with #384 to avoid duplicating the Dependabot guidance.
Would that be a useful first contribution, or is there another part you'd prefer help with?
Activity
lwasser commentedon Nov 10, 2026
I am 1000% in support of this!!
autoCAT6 commentedon Nov 13, 2026
Hi @flpm and @lwasser, I'd like to contribute to this section. Could I start with an outline for dependency security and a worked Python dependency-auditing example? I'd cover checking for known vulnerabilities, interpreting findings and documenting remediation, with links to existing guidance. I can coordinate with #384 to avoid duplicating the Dependabot guidance.
Would that be a useful first contribution, or is there another part you'd prefer help with?