We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
we have a lot of documents here, and while they claim to stick to the specs and authoritative guides, this needs to checked/reviewed manually.
what we might automate is: detect which schema version the respective examples intend to comply to, and check that they actually do this.
the following process it intended to run on each change of the default branch, as well as on every pull-request:
*.cdx.{json,xml}
$.schemaVersion
1.2.xyz
CycloneDX v1.2
+ easy to implement, as most work was done already + maintenance can be driven by dependabot/renovate - rely on the library being up-to-date
+ independent - initial development might be slow - needs manual maintenance
The text was updated successfully, but these errors were encountered:
jkowalleck
No branches or pull requests
problem
we have a lot of documents here, and while they claim to stick to the specs and authoritative guides, this needs to checked/reviewed manually.
what we might automate is:
detect which schema version the respective examples intend to comply to, and check that they actually do this.
possible solution
the following process it intended to run on each change of the default branch, as well as on every pull-request:
*.cdx.{json,xml}
-- so they are distinguished from other files in the example folders*.cdx.{json,xml}
$.schemaVersion
starts with main version - like1.2.xyz
->CycloneDX v1.2
Implementation details:
pro/cons of using existing library
pro/cons of standalone
The text was updated successfully, but these errors were encountered: