clearlydefined / clearlydefined/service
Version Control data as a schema attribute
Open
question
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
I am getting asked more often for contextual data on a given 3rd party work that is tied to the version control system. This may be more suited for the umbrella efforts like ClearlySecure, but helping to pull together all these pointers for a given work would be helpful. Maybe ClearlyMaintained aligned with the work done in CHAOSS?
Solution'ing for this is complicated I get it. Some package managers have attributes that could be harvested, but that is very hit or miss. It feels like this would be similar to how to connect a Component to a CPE for tying to the NVD.
Contributor guide
Assessment
This issue has not been assessed yet.