Create and maintain a Rust module/crate for Security Insights
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 4
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 2
Description
Overview
This would be advantageous to us as it gives better release consistency between new versions of the schema and the go and rust code in use that consumes instances of the schema.
Today, the only existing Rust implementation I'm aware of is in CLOMonitor, see https://github.com/cncf/clomonitor/blob/main/clomonitor-core/src/linter/checks/datasource/security_insights.rs, and it only supports Insightsv1.
Next Steps
- Develop Rust module supporting both v1 and v2 versions of the schema and raise PR
- Once merged and released, migrate CLOMonitor over to the new module
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
Start by reading the existing CLOMonitor implementation in clomonitor-core/src/linter/checks/datasource/security_insights.rs and compare its Insightsv1 support with the v1 and v2 schemas. Define the module's scope from those schema versions, then verify that CLOMonitor can migrate to it after the module is merged and released.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100