cyclonedx-spec-reviewer
Skill1.1k starsChanged 14 days agoApache-2.0View on GitHub
Reviews cdxgen changes for CycloneDX schema compliance, semantic field correctness, and unnecessary custom properties across spec versions 1.5 through 2.0, including AI-BOM modeling via formulation, modelCard, pedigree, and evidence. Use when a pull request changes CycloneDX output, schema handling, validators, package-manager integrations, BOM enrichment, or custom properties.
1 other project uses a version of this.
Trending
Quiet this year.about the whole repository
Most recently taken up by
- cdxgen/cdxgenword for word, first seen Oct 8, 2026
Who's talking about CycloneDX/cdxgen
- nodejs/node“npm on Windows fails with module not found for Node.js 22.0.0”GitHub · Apr 25, 2024 · 33 reactions
- CycloneDX/cyclonedx-go“Improve support for the `Component.Evidence.Identity` field in CycloneDX 1.6”GitHub · Jul 30, 2024 · 4 reactions
- cdxgen/cdxgen“Bazel build being run for non-Bazel projects, causing errors”GitHub · Sep 10, 2024 · 3 reactions
- cdxgen/cdxgen“[pnpm] Improve metadata collection with node_modules parsing”GitHub · Aug 7, 2025 · 2 reactions
- cdxgen/cdxgen“Add docs and fix for allowlist of hosts and commands”GitHub · Jun 29, 2025 · 2 reactions
The biggest 5 of 41 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 41
Talked about on GitHub and Bluesky (41 times).
On GitHub · 40
- Apr 25, 2024npm on Windows fails with module not found for Node.js 22.0.0 — nodejs/node33 reactions · 47 comments
- Jul 30, 2024Improve support for the `Component.Evidence.Identity` field in CycloneDX 1.6 — CycloneDX/cyclonedx-go4 reactions · 11 comments
- Sep 10, 2024Bazel build being run for non-Bazel projects, causing errors — cdxgen/cdxgen3 reactions · 3 comments
- Aug 7, 2025[pnpm] Improve metadata collection with node_modules parsing — cdxgen/cdxgen2 reactions · 6 comments
- Jun 29, 2025Add docs and fix for allowlist of hosts and commands — cdxgen/cdxgen2 reactions · 1 comment
35 more on GitHub
- May 1, 2025feat: make bazel query compatible with newer bazel versions and rules… — cdxgen/cdxgen2 reactions · 3 comments
- Oct 27, 2024Run some GitHub action jobs only on main repository — cdxgen/cdxgen2 reactions
- Jul 2, 2024Invalid Dotnet version detected and missing versions for the dependencies — cdxgen/cdxgen2 reactions · 12 comments
- Apr 22, 2024Add support for executing dependencies task in parallel for Gradle — cdxgen/cdxgen2 reactions · 6 comments
- Feb 1, 2024Added support for components properties filter — cdxgen/cdxgen2 reactions · 4 comments
- Dec 23, 2023[core] Improve exclude to match sub-directories — cdxgen/cdxgen2 reactions
- Oct 8, 2023Switching to java 21 — cdxgen/cdxgen2 reactions · 2 comments
- Sep 11, 2023Fix npm package deps tree — cdxgen/cdxgen2 reactions · 13 comments
- Jun 27, 20231.4 compatibility mode — cdxgen/cdxgen2 reactions
- May 26, 2023Even after setting CDX_MAVEN_INCLUDE_TEST_SCOPE=false some of the dependencies of test modules created in BOM — cdxgen/cdxgen2 reactions · 5 comments
- Oct 7, 2025Re-enable license fetching — MediaMarktSaturn/technolinator1 reaction · 1 comment
- Aug 15, 2025Extend data tracked for each package type and ecosystem with extra reference information — package-url/purl-spec1 reaction · 3 comments
- Jun 9, 2025bugfix: normalize component evidence identities to always be array — cdxgen/cdxgen1 reaction
- Jun 8, 2025Fix technique filtering logic by correctly checking for intersection — cdxgen/cdxgen1 reaction
- Apr 15, 2025Ignore uncommented lines in gradle build scripts — cdxgen/cdxgen1 reaction · 3 comments
- Feb 20, 2025Fix pnpm and yarn lock file detection — cdxgen/cdxgen1 reaction
- Jul 24, 2024Speed up SBOM generation by using newest features — apache/airflow1 reaction
- Jul 2, 2024Do not aggressively exclude while dealing with java projects — cdxgen/cdxgen1 reaction · 4 comments
- May 30, 2024Sanitize externalReferences URLs and exclude invalid ones + Strict JSON Schema validation — cdxgen/cdxgen1 reaction · 13 comments
- May 20, 2024Fix: Split linux-tests job into two jobs — cdxgen/cdxgen1 reaction
- Apr 30, 2024Adds a new workflow to generate SBOM — DefectDojo/django-DefectDojo1 reaction · 4 comments
- Apr 18, 2024Regenerate lock file and types. Adds vuln scanning — cdxgen/cdxgen1 reaction
- Mar 27, 2024cdx 1.6 spec support with some goodies — cdxgen/cdxgen1 reaction · 5 comments
- Jan 27, 2024Make 10.x branch the default — cdxgen/cdxgen1 reaction · 1 comment
- Jan 27, 2024Remove xml format — cdxgen/cdxgen1 reaction
- Nov 21, 2023Feature/nydus demo — cdxgen/cdxgen1 reaction
- Nov 16, 2023Fixes for Server params — cdxgen/cdxgen1 reaction · 5 comments
- Nov 15, 2023Support for private docker registry — cdxgen/cdxgen1 reaction · 2 comments
- Oct 23, 2023Generated license sometimes not valid according to BOM schema — cdxgen/cdxgen1 reaction · 6 comments
- Oct 12, 2023Filters and config files support — cdxgen/cdxgen1 reaction
- Jul 3, 2023MINOR: 9.1.0 release with deno, evidences and python dependency tree. 1 BREAKING change — cdxgen/cdxgen1 reaction · 2 comments
- Jun 30, 2023Provide possibility to define alternative NUGET API base url — cdxgen/cdxgen1 reaction · 3 comments
- May 29, 2023scanning setup.py doesn't work if "install_requires" is initialized to a variable instead of a list of strings — cdxgen/cdxgen1 reaction · 2 comments
- Mar 7, 2023Rendering multiple Subtrees in dependency tree tab of Dependency tracker — DependencyTrack/dependency-track1 reaction · 4 comments
- Feb 27, 2023Dependency Graph cannot be generated — cdxgen/cdxgen1 reaction · 11 comments
On Bluesky · 1
- Feb 4, 2025The first step towards #crypto #agility is to be able to make an inventory of all your crypto assets. Currently, there are no… — @seceng.bsky.social0 likes and reposts · 2 replies
Other versions1 project uses a version of this.
Word for word · 1
- cdxgen/cdxgen★ 1.1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- bom-slimmerSkill
- custom-property-authorSkill
- ecosystem-onboardingSkill
- sbom-fidelity-loopSkill
- SKILL.mdSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 9 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when a pull request changes CycloneDX output, schema handling, validators, package-manager integrations, BOM enrichment, or …
- Distinctive: line 22
When a change introduces AI-BOM, model inventory, prompt/config discovery, or agent/MCP inventory, explicitly review the standard AI/ML …
- Distinctive: line 32
Treat AI-BOM as CycloneDX-first modeling, not as permission to shift standard semantics into custom properties.
- Distinctive: line 50
If a custom property is still necessary, require a clear namespace and a narrow purpose.
- Very specific: line 78
When a PR adds or changes ecosystem support, check whether emitted components and services are missing expected data that cdxgen can …
- Distinctive: line 112
Check whether any new custom property could be replaced by a standard field.
- Distinctive: line 113
Check whether any deprecated field is newly introduced or expanded.
- Very specific: line 114
Check whether any new package-manager integration omits expected attributes that cdxgen already emits for comparable ecosystems.
- Distinctive: line 116
Check whether AI-specific custom properties duplicate standard fields such as model type, task, lineage, datasets, provider, or runtime …
- Very specific: line 117
Check spec-version downgrade and upgrade paths, especially 1.5/1.6/1.7 versus 2.0 behavior for AI-BOM structures.
- Very specific: line 140
When the intent is to show where a component was found, evidence.occurrences[].location is the more semantically correct field.
- Distinctive: line 152
Treat this as a strong signal for removal or redesign rather than a property to preserve.
- Distinctive: line 163
When reviewing new integrations, treat missing license, hash, and dependency information as expected completeness checks, not optional …
- Very specific: line 169
When a stable Hugging Face, model, or dataset identity is available, prefer durable references (bom-ref, purl, externalReferences, dataset …
- Very specific: line 170
If lineage is known only from model-repository metadata, pedigree.notes may be acceptable as supplemental context, but not as the sole …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CycloneDX specification reviewer
Use this skill when a pull request changes CycloneDX output, schema handling, validators, package-manager integrations, BOM enrichment, or custom properties.
Sources of truth
Review in this order:
- Local schemas in
data/bom-1.5.schema.json,data/bom-1.6.schema.json,data/bom-1.7.schema.json - Other local schemas when relevant, especially
data/cyclonedx-2.0-bundled.schema.json - Official CycloneDX documentation and property-taxonomy guidance
JSON-schema validity is only the starting point. Also review semantic correctness.
AI-BOM focus areas
When a change introduces AI-BOM, model inventory, prompt/config discovery, or agent/MCP inventory, explicitly review the standard AI/ML fields already present in CycloneDX 1.5, 1.6, 1.7, and 2.0.
formulationpedigreemodelCarddatacomponents andcomponentDataservicesevidenceexternalReferences
Treat AI-BOM as CycloneDX-first modeling, not as permission to shift standard semantics into custom properties.
What to check
1. Prefer standard fields over custom properties
Flag a change when it introduces or preserves a custom property for data that already fits a standard field such as:
supplier,manufacturer,authors,publisherexternalReferencesevidence.identityevidence.occurrencespedigreehasheslicensesscopepropertiesregistered in public taxonomy when applicable
If a custom property is still necessary, require a clear namespace and a narrow purpose.
2. Reject ambiguous or risky custom properties
Flag custom properties that are:
- unnamespaced
- duplicates of existing CycloneDX fields
- host-specific or non-reproducible
- likely to leak local paths, usernames, secrets, or environment-specific details
- packing structured data into comma-delimited strings when a structured field exists
- likely to confuse downstream consumers about meaning
3. Check semantic field use
Review whether attributes are used for the right purpose:
manufacturerfor the entity that created the componentsupplierfor the entity that supplied or distributed itauthorsfor people, not organizations- deprecated
authoronly as a compatibility holdover and preferably not in new output publisheronly when publication semantics are actually intendedexternalReferences[].typematches the URL purposescopeis semantically correct for required, optional, excluded, or runtime-only style databom-refvalues are unique and resolvable
4. Check new ecosystem/package-manager integrations
When a PR adds or changes ecosystem support, check whether emitted components and services are missing expected data that cdxgen can usually infer:
- stable
bom-ref type,name,version- purl when a native package identity exists
- dependency edges
- hashes when resolved artifacts or lockfile integrity data are available
- licenses when manifest or registry metadata provides them
externalReferencesfor distribution or VCS when directly available- evidence fields when provenance or file-location evidence is collected
Flag missing data as a gap when the source material is already available to the integration.
5. Check AI-BOM and AI/ML modeling
Review whether AI-related output uses the standard CycloneDX AI/ML structures correctly:
formulationshould describe how something was created, trained, assembled, deployed, or otherwise brought into its current form. Do not treat it as a generic dumping ground for unrelated inventory.formulation.workflows,tasks, andstepsshould represent real process information. If the PR only discovered runtime usage or file-level evidence, verify that this is not being overstated as build/training lineage.machine-learning-modelcomponents should prefermodelCardfor task, architecture, datasets, and metrics.- training or evaluation datasets should prefer
modelCard.modelParameters.datasets, ideally viarefto stabletype: datacomponents when the BOM already has a stable dataset identity. - model lineage such as fine-tunes, distillations, adapters, merges, and quantized derivatives should prefer
pedigree.ancestors,pedigree.variants,commits, orpatches. Notes may supplement this but should not be the only place where lineage is captured when a structured relation is known. - inference endpoints belong in
services, notcomponents. - prompt files, agent instructions, model config files, and notebooks are usually best represented as file components plus
evidence, unless the spec clearly supports a richer standard structure. component.datamust only be present fortype: datacomponents.component.modelCardshould only be present fortype: machine-learning-model.- service
evidenceand any 2.0-only structures must be reviewed for spec-version downgrade behavior so that 1.5/1.6/1.7 output does not silently become semantically misleading.
Also review AI-specific custom properties carefully. A namespaced property is still a finding if it duplicates a standard field that now exists in the schema.
Review procedure
- Identify the spec version(s) affected by the change.
- Compare changed output fields against the local schema definitions.
- Check whether any new custom property could be replaced by a standard field.
- Check whether any deprecated field is newly introduced or expanded.
- Check whether any new package-manager integration omits expected attributes that cdxgen already emits for comparable ecosystems.
- For AI-BOM changes, compare every emitted AI field against
formulation,modelCard,pedigree,componentData,services, andevidencein the local schemas. - Check whether AI-specific custom properties duplicate standard fields such as model type, task, lineage, datasets, provider, or runtime endpoints.
- Check spec-version downgrade and upgrade paths, especially 1.5/1.6/1.7 versus 2.0 behavior for AI-BOM structures.
- Produce findings in four groups:
spec violation,semantic misuse,unnecessary customization, andexpected data missing.
Expected review output
For every finding, include:
- exact field or property name
- why it is a problem
- preferred CycloneDX field or modeling approach
- schema/spec basis
- whether it is a repo-wide legacy pattern or introduced by the PR
Repo calibration findings
These repo-specific findings were identified while calibrating this skill and should be treated as known review heuristics.
- Self-generated BOMs for this repository currently expose three unnamespaced custom property names:
internal:SrcFile,internal:ImportedModules, andinternal:LocalNodeModulesPath.
Iteration 1: legacy internal:SrcFile property
- Current cdxgen output emits unnamespaced
internal:SrcFileproperties. - In self-generated BOMs this often duplicates
evidence.identity[].methods[].value. - When the intent is to show where a component was found,
evidence.occurrences[].locationis the more semantically correct field.
Iteration 2: legacy internal:ImportedModules property
- Current cdxgen output emits unnamespaced
internal:ImportedModules. - The value is packed as CSV-like text and mixes module names with symbol-like data.
- This is hard for downstream tooling to interpret and should be reviewed against
evidence.occurrencesplussymbol, or replaced with a clearly namespaced property if no standard field fits.
Iteration 3: legacy internal:LocalNodeModulesPath property
- Current cdxgen output emits unnamespaced
internal:LocalNodeModulesPath. - It can contain absolute host paths, which are environment-specific and potentially sensitive.
- Treat this as a strong signal for removal or redesign rather than a property to preserve.
Iteration 4: deprecated and incomplete producer metadata
- Current output may rely on deprecated
metadata.component.authorinstead ofauthorsormanufacturer. - Root BOM metadata commonly has
metadata.authorsbut notmetadata.supplier. - For published artifacts, review whether
supplierand contact/manufacturer data should be emitted instead of or in addition to author-style fields.
Iteration 5: completeness gaps for emitted components
- Self-validation of a generated BOM for this repository still shows components missing license data and at least one component missing hashes/dependency linkage.
- When reviewing new integrations, treat missing license, hash, and dependency information as expected completeness checks, not optional polish, if the upstream ecosystem exposes that data.
Iteration 6: AI-BOM review heuristics
cdx:ai:*properties are namespaced and therefore better than unnamespaced properties, but they should still be challenged when they duplicate standard CycloneDX AI/ML fields.- In particular, review whether task, lineage, datasets, provider identity, runtime identity, and variant classification should move to
modelCard,pedigree,externalReferences,services, orevidence. - When a stable Hugging Face, model, or dataset identity is available, prefer durable references (
bom-ref, purl,externalReferences, dataset refs) over free-text notes. - If lineage is known only from model-repository metadata,
pedigree.notesmay be acceptable as supplemental context, but not as the sole representation when the relation itself is structured and reproducible.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

