custom-property-author
Skill1.1k starsChanged 14 days agoApache-2.0View on GitHub
Guides defining and emitting new CycloneDX cdx: custom properties in cdxgen output, enforcing namespacing, safe value shapes (booleans, counts, categories instead of raw secrets, URLs, or commands), and the mandatory docs/CUSTOM_PROPERTIES.md documentation gate. Use when adding, changing, or reviewing cdx: or internal: properties on components, metadata, services, or evidence.
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- CycloneDX/cdxgenword for word, first seen Oct 9, 2026
Who's talking about cdxgen/cdxgen
- Attraccess/Attraccess“chore(deps): update dependency @cyclonedx/cdxgen to v12.8.5”GitHub · Oct 4, 2026 · 1 reactions
- owasp-dep-scan/dep-scan“Bug: the pre-build stage of lifecycle analysis passes --deep to cdxgen”GitHub · Oct 3, 2026 · 1 reactions
- sudosubin/agents.nix“codex-marketplaces.github.cdxgen.cdxgen: 13.7.0 → 13.8.0”GitHub · Nov 14, 2026
- sudosubin/agents.nix“codex-plugins.github.cdxgen.cdxgen: 13.7.0 → 13.8.0”GitHub · Nov 14, 2026
- sudosubin/agents.nix“claude-code-marketplaces.github.cdxgen.cdxgen: 13.7.0 → 13.8.0”GitHub · Nov 14, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Oct 4, 2026chore(deps): update dependency @cyclonedx/cdxgen to v12.8.5 — Attraccess/Attraccess1 reaction · 3 comments
- Oct 3, 2026Bug: the pre-build stage of lifecycle analysis passes --deep to cdxgen — owasp-dep-scan/dep-scan1 reaction
- Nov 14, 2026codex-marketplaces.github.cdxgen.cdxgen: 13.7.0 → 13.8.0 — sudosubin/agents.nix0 reactions
- Nov 14, 2026codex-plugins.github.cdxgen.cdxgen: 13.7.0 → 13.8.0 — sudosubin/agents.nix0 reactions
- Nov 14, 2026claude-code-marketplaces.github.cdxgen.cdxgen: 13.7.0 → 13.8.0 — sudosubin/agents.nix0 reactions
45 more on GitHub
- Nov 14, 2026claude-code-plugins.github.cdxgen.cdxgen: 13.7.0 → 13.8.0 — sudosubin/agents.nix0 reactions
- Nov 13, 2026Update dependency @cyclonedx/cdxgen to v12.9.2 — digicatapult/shared-workflows0 reactions
- Nov 9, 2026HBoM-cdxgen: update to latest version in nixpkgs — ngi-nix/projects0 reactions · 1 comment
- Nov 8, 2026codex-plugins.github.cdxgen.cdxgen: init at 13.7.0 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-plugins.github.cdxgen.cdxgen: 13.6.0 → 13.7.0 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-marketplaces.github.cdxgen.cdxgen: 13.6.0 → 13.7.0 — sudosubin/agents.nix0 reactions
- Nov 7, 2026codex-marketplaces.github.cdxgen.cdxgen: 13.6.0 → 13.7.0 — sudosubin/agents.nix0 reactions
- Nov 7, 2026codex-marketplaces.github.cdxgen.cdxgen: init at 13.6.0 — sudosubin/agents.nix0 reactions
- Oct 31, 2026claude-code-marketplaces.github.cdxgen.cdxgen: 13.5.0 → 13.6.0 — sudosubin/agents.nix0 reactions
- Oct 31, 2026claude-code-plugins.github.cdxgen.cdxgen: 13.5.0 → 13.6.0 — sudosubin/agents.nix0 reactions
- Oct 30, 2026Ask for Reported-by and Helped-by credits in CONTRIBUTING and the PR template — owasp-dep-scan/.github0 reactions
- Oct 30, 2026Ask for Reported-by and Helped-by credits in CONTRIBUTING and the PR template — cdxgen/.github0 reactions
- Oct 30, 2026Add an AGENTS.md that asks for Reported-by and Helped-by credits — AppThreat/atom-tools0 reactions
- Oct 30, 2026Add an AGENTS.md that asks for Reported-by and Helped-by credits — AppThreat/atom0 reactions
- Oct 30, 2026Add an AGENTS.md that asks for Reported-by and Helped-by credits — AppThreat/chen0 reactions
- Oct 30, 2026Ask agents to credit reporters and helpers with commit trailers — owasp-dep-scan/blint0 reactions
- Oct 30, 2026Ask agents to credit reporters and helpers with commit trailers — owasp-dep-scan/dep-scan0 reactions
- Oct 30, 2026Ask agents to credit contributors, and remove a flaky Roslyn test — owasp-dep-scan/dosai0 reactions
- Oct 30, 2026Update catalogue links that point at renamed repositories — MustacheCase/zanadir0 reactions · 1 comment
- Oct 30, 2026chore(deps-dev): bump the npm-development-minor-patch group with 3 updates — navikt/sf-cli-plugin-pool0 reactions
- Oct 29, 2026fix(security/medium/formula/c): update homebrew formula @cyclonedx/cdxgen to v12 [security] — grafana/homebrew-core0 reactions · 1 comment
- Oct 27, 2026chore: bump @cyclonedx/cdxgen from 12.8.6 to 12.9.0 — sbomify/sbom-tools0 reactions
- Oct 26, 2026chore(deps-dev): bump the development-tooling group across 1 directory with 15 updates — killedoxygen/mail-edge0 reactions · 1 comment
- Oct 26, 2026build(deps-dev): Bump @cyclonedx/cdxgen from 11.11.0 to 12.9.0 — TomasSilva20451/SaveVision0 reactions
- Oct 22, 2026chore(deps-dev): bump @cyclonedx/cdxgen from 12.8.5 to 12.8.6 in the npm-development-minor-patch group — navikt/sf-cli-plugin-pool0 reactions
- Oct 20, 2026chore(deps-dev): bump the development-dependencies group across 1 directory with 17 updates — WeKIKO/monoplate0 reactions
- Oct 16, 2026Registry doesnt work with license scanning tools. — coder/registry0 reactions · 3 comments
- Oct 14, 2026chore(deps-dev): bump @cyclonedx/cdxgen from 11.11.0 to 12.8.5 — ochairo/databehave0 reactions · 1 comment
- Oct 13, 2026ci(deps): bump @cyclonedx/cdxgen from 12.8.4 to 12.8.5 in /tools/github-workflow-tools in the node-workflow-tools group — eclipse-csi/codesign-tools0 reactions · 1 comment
- Oct 9, 2026chore(deps-dev): bump the dev-deps-patch group across 1 directory with 2 updates — kalebteccom/browxai0 reactions · 1 comment
- Oct 7, 2026chore(deps-dev): bump @cyclonedx/cdxgen from 12.8.4 to 12.8.5 in the npm-development-minor-patch group — navikt/sf-cli-plugin-pool0 reactions
- Oct 6, 2026chore: bump @cyclonedx/cdxgen from 12.8.4 to 12.8.5 — sbomify/sbom-tools0 reactions
- Oct 6, 2026Update PURL mappings for conda-forge packages — prefix-dev/purl-associator0 reactions · 2 comments
- Oct 5, 2026chore(deps-dev): bump @cyclonedx/cdxgen from 11.8.0 to 12.8.5 — Noel-Schmidt/snappo0 reactions
- Oct 4, 2026crypto fails with OutOfMemoryException once its JSON passes 2 GB, and cdxgen drops it from 512 MB — owasp-dep-scan/dosai0 reactions
- Oct 2, 2026chore(deps-dev): bump @cyclonedx/cdxgen from 12.8.4 to 12.8.5 — kaoto-archive/vscode-kaoto0 reactions
- Sep 30, 2026cdxgen: 13.0.1 -> 13.7.0 — NixOS/nixpkgs0 reactions · 13 comments
- Sep 28, 2026chore(deps-dev): bump the dev-dependencies group across 1 directory with 22 updates — munderhaug/Saldo0 reactions
- Sep 27, 2026Proposal: add a read-only SRAC safety-context workflow — endorlabs/endorlabs-sdk0 reactions · 1 comment
- Sep 27, 2026[FR] [Mend SBOM CLI] Add optional SRAC safety-relevance enrichment — mend-toolkit/Mend-SBOM-Export-CLI0 reactions
- Sep 27, 2026✨ Integrate SRAC safety relevance with SBOM and SCA findings — xygeni/xygeni0 reactions
- Sep 27, 2026Proposal: enrich vulnerability reports with SRAC safety relevance — devops-kung-fu/bomber0 reactions
- Sep 14, 2026chore(deps-dev): bump the dev-deps group across 1 directory with 24 updates — smonn/ids0 reactions · 2 comments
- Aug 31, 2026chore(deps-dev): bump the development-dependencies group across 2 directories with 8 updates — woowabros/critical-script0 reactions · 1 comment
- Aug 24, 2026build(deps-dev): bump @cyclonedx/cdxgen from 12.8.0 to 12.8.4 — farshadf/OpenMermaid0 reactions · 1 comment
Other versions1 project uses a version of this.
Word for word · 1
- CycloneDX/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
- cyclonedx-spec-reviewerSkill
- ecosystem-onboardingSkill
- sbom-fidelity-loopSkill
- SKILL.mdSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when adding or changing any cdx:* (or internal:*) property emitted into BOM output.
- Distinctive: line 22
If a standard field works, use it.
- Distinctive: line 32
Treat every value as potentially secret-bearing.
- Very specific: line 48
Add it to the appropriate property-family table (or inventory section) in docs/CUSTOM_PROPERTIES.md, with the value shape and a …
- Distinctive: line 49
Add or extend a test asserting the new property is emitted as expected and that secrets are not copied into it.
- Very specific: line 50
If the property creates an analyst pivot, check companion surfaces that stay aligned: BOM audit rules in data/rules/*.yaml, …
≈ “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
Custom property author
Use this skill when adding or changing any cdx:* (or internal:*) property emitted into BOM output. The full property inventory and policy guidance is docs/CUSTOM_PROPERTIES.md.
Gate 0: prefer standard CycloneDX fields first
A custom property is a last resort. Before adding one, check whether the data fits a standard field:
supplier,manufacturer,authors,publisher— entity dataexternalReferences— URLsevidence.identity,evidence.occurrences— where a component was foundpedigree— lineagehashes— digests (never a property)licenses,scope— licensing and dependency scopemodelCard,formulation,component.data— AI/ML data
If a standard field works, use it. If a custom property is still necessary, it needs a clear namespace and a narrow purpose.
Gate 1: naming
- New properties use the
cdx:<ecosystem-or-context>:<field>convention (e.g.cdx:npm:hasInstallScript,cdx:github:workflow:triggers). - Legacy unnamespaced properties were migrated to the
internal:prefix; do not add new unnamespaced properties, and treatinternal:*as unstable implementation detail. oci:andjava:moduleskeep their existing namespaces for historical reasons.
Gate 2: value hygiene
Treat every value as potentially secret-bearing. CycloneDX serializes all property values as strings.
| Emit | Do NOT emit |
Booleans: credentialExposure=true | Raw tokens, passwords, API keys, cookies, session IDs, private keys |
Counts: credentialIndicatorCount=3 | Raw environment variable values or command-line arguments |
Categories/field labels: header:Authorization | The actual header/parameter values |
| Safe URL derivatives: scheme, host, basename | URLs with query strings, fragments, userinfo, or signature params (token, sig, X-Amz-Signature, api_key, …) |
| Redacted markers or executable name only | Full command lines, generated source contents, embedded file contents |
Value shapes already in use (keep consistent): booleans as "true"/"false", numbers as decimal strings, component-level lists comma-separated, BOM-level metadata lists newline-separated, timestamps as ISO 8601, structured payloads as JSON-serialized strings.
Gate 3: documentation (build-breaking)
lib/customProperties.poku.js scans every string literal matching cdx:... in non-test lib/**/*.js and fails the build if the property is absent from docs/CUSTOM_PROPERTIES.md. When adding a property:
- Add it to the appropriate property-family table (or inventory section) in
docs/CUSTOM_PROPERTIES.md, with the value shape and a policy-readiness label (hard deny / warning / context only). - Add or extend a test asserting the new property is emitted as expected and that secrets are not copied into it.
- If the property creates an analyst pivot, check companion surfaces that stay aligned: BOM audit rules in
data/rules/*.yaml,docs/BOM_AUDIT.md, andbin/repl.jscommands.
Review quick-check
- Unnamespaced or new
internal:property? Reject. - Duplicates a standard CycloneDX field? Move to the standard field.
- Host-specific, non-reproducible, absolute local paths? Reject or redact.
- Structured data packed into CSV when a structured field exists? Reject.
- Secret-bearing value (even namespaced)? Replace with a count, boolean, host, or enum.
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.

