docs: describe partial-credit pass range for dependency_security - #541
Conversation
The dependency_security section claimed a flat pass threshold of 60 points, but DependencySecurityAssessor passes any score >= 30: scores of 30-59 pass with partial credit and attached remediation, and only scores below 30 fail. Update docs/attributes.md to match the code. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe Dependency Security documentation now defines three score bands: full pass, partial credit with remediation guidance, and failure. ChangesDependency Security documentation
Merge Risk: ⚪ Minimal · up to Dependency Security documentation now clearly describes full-pass, partial-credit, and failing score bands. No remaining merge-readiness risk is identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
📈 Test Coverage Report
Coverage calculated from unit tests only |
Summary
The
dependency_securityentry indocs/attributes.mdstated a flat "Pass threshold: 60 points," butDependencySecurityAssessorinsrc/agentready/assessors/security.pypasses any score of 30 or higher. Scores of 30-59 are partial-credit passes with remediation guidance attached to the finding, and only scores below 30 fail.This updates the docs to describe the actual behavior:
Docs-only change; no assessor behavior is modified.
This PR was created by Bill Murdock with assistance from Claude Code.
🤖 Generated with Claude Code
Summary by CodeRabbit