Add AGENTS.md + SECURITY.md pointing to the Drill security model#56
Open
potiuk wants to merge 1 commit into
Open
Add AGENTS.md + SECURITY.md pointing to the Drill security model#56potiuk wants to merge 1 commit into
potiuk wants to merge 1 commit into
Conversation
Generated-by: Claude Code
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.
This is a proposal for the PMC to review — please correct, reject, or
discuss as needed. Nothing here is a requirement; the maintainer is the
decision-maker.
This adds a minimal
AGENTS.md+SECURITY.mdto the Drill website repo soan automated scan agent can mechanically discover the project's security model
via the conventional
AGENTS.md → SECURITY.md → threat modelchain.apache/drill-siteis the project website; the actual security model lives inthe main
apache/drillrepository, so these files just point there (theproject's umbrella model) rather than duplicating it. Nothing about the model
content changes — this is only the discoverability wiring.
Context: the ASF Security team is preparing the project for an automated
agentic security scan we're piloting. Such scans refuse to run if the model
isn't discoverable by that path (refusing upfront beats a noise-heavy run
against a model the agent never found). This is the website-repo companion to
the model that already merged on
apache/drill; wiring the site repo toomeans the full requested scope is discoverable.
Questions / pushback welcome — happy to adjust the wording, or to drop the
site repo from scope entirely if you'd rather not include it in the scan.