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
To store decentralized scans, vulnerabilities and other package metadata, we need to define the models and data schema and corresponding on-disk tree structures.
As outcome I would like to be able to automatically push individual records from PurlDB or VulnerableCode (VCIO) for a Package to a git repository, and this on each update, using a properly documented format using a JSON schema.
This would mean we would:
One of the difficulties is to cope with some of the limitations of public git services that may limit the size of a git repo AND the practical limit of git for an efficient usage where very large repos with too many files are difficult and slow to clone and use.
Another difficulty is to achieve some form of PURL-based addressing, such that a stored scan can be accessed easily based on a PURL and a minimal external knowledge of the system.
The text was updated successfully, but these errors were encountered:
To store decentralized scans, vulnerabilities and other package metadata, we need to define the models and data schema and corresponding on-disk tree structures.
As outcome I would like to be able to automatically push individual records from PurlDB or VulnerableCode (VCIO) for a Package to a git repository, and this on each update, using a properly documented format using a JSON schema.
This would mean we would:
One of the difficulties is to cope with some of the limitations of public git services that may limit the size of a git repo AND the practical limit of git for an efficient usage where very large repos with too many files are difficult and slow to clone and use.
Another difficulty is to achieve some form of PURL-based addressing, such that a stored scan can be accessed easily based on a PURL and a minimal external knowledge of the system.
The text was updated successfully, but these errors were encountered: