docs: add agent guidance and threat model - #2828
Open
smoelius wants to merge 1 commit into
Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2828 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 114 114
Lines 2600 2600
Branches 659 659
=========================================
Hits 2600 2600 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Add
AGENTS.mdwith repository-specific guidance for coding agents, including theproject layout, build and test workflows, change discipline, and standards for
security analysis and reproduction.
Add
THREAT_MODEL.mdto document validator.js's security boundaries, expectedproperties, threat scenarios, possible controls, and non-binding guidance for
reviewing and classifying findings. The threat model also clarifies the
responsibilities retained by applications integrating validator.js.
This PR changes documentation only; it does not alter the public API, runtime
behavior, generated distributions, or package contents.
References used to describe the project and its security and release boundaries:
README.mdSECURITY.mdpackage.jsonChecklist