awslabs / awslabs/simple-code-scanning-pipeline
Checkov doesn't explain why it can pass with failures -- call out the minimum criticality better
Open
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
Research direction
The issue body does not identify a file, test, or entry point. Start by locating the Checkov configuration and the documentation or output path that explains pass/fail results; done means clearly stating why failures can coexist with a pass and identifying the minimum criticality threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100