Restructure SECURITY.md into a full security policy - #67
Merged
Conversation
Split the page into four sections: supported versions (the 1.x release line), private reporting through the Apache Commons Security Page, the library threat model reports are triaged against, and the supply-chain trust assumptions of the repository workflows. The latter documents that apache/commons-* repositories are fully trusted and that trusting GitHub-owned actions/* and github/* actions is an accepted risk, so reports about unpinned references into either are out of scope. Assisted-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CLnTBsvmYtxzNTWVGNyz33
ppkarwasz
force-pushed
the
docs/security-policy
branch
from
September 1, 2026 09:05
f3c094b to
1ddff00
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restructures
SECURITY.mdfrom two bare links into four sections:apache/commons-*repositories are fully trusted (same project, governance, and access controls), and trusting GitHub-ownedactions/*andgithub/*is an accepted risk, since GitHub already runs the workflows and holds the secrets. Reports about unpinned (branch/tag) references into either are out of scope.🤖 Generated with Claude Code