anchore / anchore/vulnerability-data-tools
Where should the automation/APIs live?
Open
- Dominant language
- Python
- Stars
- 19
- Forks
- 5
- Avg merge
- 3m
- Merged PRs (30d)
- 16
Description
Are you folks planning to use github actions for generating/updating the data. Also, will you use a github site as a crude http server for this data to allow folks to more easily consume/look up this data?
Here's an example I've seen, for kubernetes yamls
https://github.com/yannh/kubernetes-json-schema/tree/master/.github/workflows
Contributor guide
Research direction
No files, tests, or entry points are named. First determine whether GitHub Actions should generate or update the data and whether a GitHub-hosted site or API should serve it; done requires an agreed automation and distribution design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100