-
Notifications
You must be signed in to change notification settings - Fork 111
feat: add Root app feed #376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
rootio/rootio.go
Outdated
| osFeedPath = "external/os_feed" // OS packages feed | ||
| appFeedPath = "external/app_feed" // Language/app packages feed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can I download the new files for testing?
Only https://api.root.io/external/cve_feed is available.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Youre right. Its being developed at the same time. I want to validate the PRs are accepted and I'll merge it on our side before merging the Trivy ones
|
And can you add the PR description, please? |
- Replace []feedInfo with map[string]string (endpoint → subdir). - Introduce feedFileName = "cve_feed.json" for consistency. - Change fetchAndSaveFeed to use (apiPath, subdir) parameters. - Always create target dir via os.MkdirAll(rootio/). - Minor cleanups: consistent err assignment and options loop.
|
hello @chait-slim Can you re-check? |
Hi, I've rechecked. From my end its approved. I've updated the tests with the real use cases of how versioning will look like in the app feed. Tomorrow morning the new API will be running |
Summary
This PR adds support for Root.io application-level vulnerability feeds to vuln-list-update, extending the existing OS-level vulnerability tracking with language/framework-specific vulnerability data.
Changes Introduced
Both feeds use the same JSON structure:
Directory Structure
After running the updater, the vulnerability data is organized as:
Testing