docs: add agent guidance and threat model - #2828
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 2598 -2
Branches 659 658 -1
=========================================
- Hits 2600 2598 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
tux-tn
left a comment
There was a problem hiding this comment.
Overall, this is a useful addition, especially as we receive more AI-assisted contributions. I also added a suggestion regarding the Node.js guidance
Co-authored-by: Sarhan Aissi <github@tux.tn>
|
@tux-tn Sorry for the delay. I applied your suggestion. Please let me know if there are any additional changes you would like made. |
tux-tn
left a comment
There was a problem hiding this comment.
Thank you for addressing my suggestion. The rest looks good to me. Let’s see if the other maintainers have any additional feedback.
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