You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fedcode-next: New and updated schemas to store enriched vulnerability data in FederatedCode #67
@pombredanne Can you clarify what exactly we need to update in order to store enriched vulnerability data in the FederatedCode model?
Currently, we are only storing the VCID, which points to a file in a Git repository, and we track all file changes using Git.
Do we need to create or update the data schemas and models to store the full vulnerability data records?
My thought is that we are storing the enriched vulnerability data through a FederatedCode curation review. Then, once a vulnerability review is accepted and the PR is merged into VulnerableCode-data, FederatedCode could federate the changes. Finally, we could make VulnerableCode import this enriched data with high-trust importer/improver.
Activity
ziadhany commentedon Aug 16, 2025
@pombredanne Can you clarify what exactly we need to update in order to store enriched vulnerability data in the FederatedCode model?
Currently, we are only storing the VCID, which points to a file in a Git repository, and we track all file changes using Git.
Do we need to create or update the data schemas and models to store the full vulnerability data records?
My thought is that we are storing the enriched vulnerability data through a FederatedCode curation review. Then, once a vulnerability review is accepted and the PR is merged into VulnerableCode-data, FederatedCode could federate the changes. Finally, we could make VulnerableCode import this enriched data with high-trust importer/improver.
feat: add schema for federated advisory data
feat: add schema for federated advisory data
feat: add schema for federated advisory data
pombredanne commentedon Aug 3, 2026
This is done.
The corresponding pull request is at:
The JSON schema is at:
Note that we use the draft-07 version JSON schema for maximum compatibility with tools.