PLSysSec / PLSysSec/cargo-scan
Severity labels + continuous integration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
another idea from @deian
For automated scans, would be cool to classify severity: e.g. Critical, High, Moderate, Low.
This could be integrated with a CI run of cargo scan to determine if any prior audits/policy saves are critically broken and help triage errors.
Similar to this:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by locating the automated scan flow and the handling of prior audits or policy saves, then review how cargo scan could run in CI. Done should include an agreed severity classification and a defined CI result for critically broken audits or policies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100