Repository navigation
docs: replace finding with assessment in the readme - #72
Merged
phantinuss merged 2 commits intoOct 14, 2026
Merged
Conversation
secDre4mer
reviewed
Oct 13, 2026
phantinuss
approved these changes
Oct 14, 2026
There was a problem hiding this comment.
🟢 Approval recommended
The documentation accurately reflects the existing v3 API and event model.
0 open findings
What changed in this PR
Updates README terminology to match the v3 Assessment model.
Changes:
- Replaces “finding” with “assessment.”
- Documents assessment scores, reasons, subjects, and ancestors.
| File | Description |
|---|---|
| README.md | Aligns v3 documentation with current assessment terminology. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
phantinuss
approved these changes
Oct 14, 2026
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.
No description provided.