chipsalliance / chipsalliance/mjolnir
Vulnerabilities Storage Format
Open
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 13h 9m
- Merged PRs (30d)
- 22
Description
Results, right now, are saved to local JSON files and are deployed by hand.
Eventually, we may want to store vulnerabilities in a more structured DB-like service.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing where vulnerability results are written to local JSON files and how they are deployed by hand. The issue names no files, service, requirements, or acceptance criteria, so clarify the storage design and what completion should mean before identifying implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100