bom-convert-validate
/bom-convert-validate
Konwertuje SBOM-y CycloneDX do SPDX 3.0.1 lub między wersjami CycloneDX, waliduje je i sprawdza zgodność z SCVS i CRA.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 4
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Konwertuje SBOM-y CycloneDX do SPDX 3.0.1 lub między wersjami CycloneDX, waliduje je i sprawdza zgodność z SCVS i CRA.
Oryginalny opis (EN)
Converts CycloneDX BOMs to SPDX 3.0.1 JSON-LD or between CycloneDX spec versions with cdx-convert, and validates BOMs against JSON schema, deep consistency checks, and OWASP SCVS and EU Cyber Resilience Act compliance benchmarks with cdx-validate, emitting SARIF for code scanning. Use when asked to convert an SBOM to SPDX, downgrade or upgrade a BOM spec version, validate or lint a BOM, check SCVS or CRA compliance, or score SBOM quality.
Jak działa
- Convert
- Validate
- Validation during generation
- Reference
Podgląd SKILL.md
--- name: bom-convert-validate description: Converts CycloneDX BOMs to SPDX 3.0.1 JSON-LD or between CycloneDX spec versions with cdx-convert, and validates BOMs against JSON schema, deep consistency checks, and OWASP SCVS and EU Cyber Resilience Act compliance benchmarks with cdx-validate, emitting SARIF for code scanning. Use when asked to convert an SBOM to SPDX, downgrade or upgrade a BOM spec version, validate or lint a BOM, check SCVS or CRA compliance, or score SBOM quality. --- # Convert and validate BOMs Two post-processing commands for BOMs that already exist. Read [reference/safety.md](../../reference/safety.md) first. ## Convert ```bash # CycloneDX to SPDX 3.0.1 JSON-LD (default target) cdx-convert -i /absolute/path/to/bom.json -o /absolute/path/to/bom.spdx.json # Cross-convert between CycloneDX spec versions cdx-convert -i /absolute/path/to/bom.json --to 1.6 -o /absolute/path/to/bom.1.6.json ``` | Flag | Purpose | | ---------------- | -------------------------------------------------------------------- | | `-i, --input` | Source BOM | | `-o, --output` | Destination | | `--to` | `spdx` (default) or a CycloneDX version: `1.5`, `1.6`, `1.7` | | `--validate` | Validate the conversion result | | `--json-pretty` | Pretty-print output | ### The legacy spec-version path `cdxgen` **rejects `1.4` and `1.5` as generation targets** — only `1.6`, `1.7` (default), and `2.0` are accepted. When a consumer needs an older document, the supported route is to generate at a valid version and downgrade the serialized output here: ```bash cdxgen -o /absolute/path/to/bom.json /absolute/path/to/project cdx-convert -i /absolute/path/to/bom.json --to 1.5 -o /absolute/path/to/bom.1.5.json ``` Tell the user that a downgrade drops fields the older schema cannot express. A 1.5 document converted from 1.7 is not the same document. ### SPDX directly from source If SPDX is the only target, skip the round trip: ```bash cdxgen --format spdx -o /absolute/path/to/bom.spdx.json /absolute/path/to/project ``` `spdxgen` is the dedicated command for the same thing. Use `cdx-convert` when the CycloneDX document already exists or is also wanted. ## Validate ```bash cdx-validate -i /absolute/path/to/bom.json ``` Three layers run together: 1. **Schema validation** — CycloneDX JSON schema 2. **Deep validation** — metadata, purl, `bom-ref`, and property consistency 3. **Compliance rule packs** — OWASP SCVS (all 87 controls across L1/L2/L3) and EU Cyber Resilience Act SBOM expectations (8 controls) Protobuf input works too: ```bash cdx-validate -i /absolute/path/to/bom.cdx ``` ### Compliance benchmarks ```bash cdx-validate -i /absolute/path/to/bom.json --benchmark scvs-l2 -r sarif -o /absolute/path/to/results.sarif ``` Benchmark aliases: `scvs`, `scvs-l1`, `scvs-l2`, `scvs-l3`, `cra`. Defaults to all. Categories: `compliance-scvs`, `compliance-cra`. Rules that cannot be decided from a BOM alone — "SBOMs are required for new procurements", for example — are surfaced as **manual-review** items so coverage is still tracked. Include them with `--include-manual`. This matters when reporting a score: a control marked manual-review is neither passing nor failing. Do not fold it into either bucket. ### Validation flags | Flag | Purpose | | --------------------- | ------------------------------------------------------------------ | | `--schema` / `--no-schema` | JSON-schema layer, on by default | | `--deep` | Deep consistency checks | | `--benchmark, -b` | Compliance benchmarks to score | | `--categories` | Compliance rule categories | | `--strict` | Treat warnings as failures | | `--min-severity` | Minimum severity to report | | `--fail-severity` | Severity that causes a non-zero exit | | `--include-manual` | Include manual-review controls in output | | `--include-pass` | Show passing controls, not just failures | | `--report, -r` | `sarif` and other formats | | `--report-file, -o` | Write the report to a file | | `--public-key` | Verify the JSF signature during validation | | `--require-signature` | Fail unless the signature verifies; needs a key, exit 1 without one | | `--platform` | Platform-specific validation behaviour | ### Release-gate pattern ```bash cdx-validate -i /absolute/path/to/bom.json \ --benchmark scvs-l2,cra \ --public-key /absolute/path/to/public.pem --require-signature \ --strict \ -r sarif -o /absolute/path/to/results.sarif ``` Schema, deep consistency, SCVS L2, CRA, and signature presence in one gate. ## Validation during generation `cdxgen --validate` is on by default, so a generated BOM is already schema-checked. `cdx-validate` adds the deep and compliance layers, which generation does not run. Do not tell the user their BOM is "already validated" when they are asking about SCVS or CRA coverage. Rule details: <https://cdxgen.github.io/cdxgen/#/VALIDATION_RULES>. ## Reference - Conversion: <https://cdxgen.github.io/cdxgen/#/CDX_CONVERT> - Validation: <https://cdxgen.github.io/cdxgen/#/CDX_VALIDATE> - Validation rules: <https://cdxgen.github.io/cdxgen/#/VALIDATION_RULES>
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · cdxgen/cdxgen | 100 | Apache-2.0 |
| cdxgen/cdxgen | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki e2fbcedc66e9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100software-bill-of-materials-sbom-spdx-cyclonedx
Generuje i audytuje listę składników oprogramowania (SBOM) w standardach SPDX i CycloneDX. - 100bom-audit
Analizuje ryzyko łańcucha dostaw w BOM CycloneDX narzędziami cdx-audit i cdxgen: kompromitacja pakietów npm i PyPI, uprawnienia CI, integralność źródeł, licencje oraz raporty SARIF lub JSON. - 96bom
Tworzy AI-BOM w formacie CycloneDX lub SPDX dla agentów, serwerów MCP, projektów i kont chmurowych, z podatnościami. - 100bom-signing
Podpisuje i weryfikuje BOM CycloneDX natywnym formatem JSON Signature Format przez cdx-sign i cdx-verify, w tym podpisy komponentów, usług i adnotacji oraz łańcuchy podpisów. - 100bom
Generuje AI-BOM w formacie CycloneDX lub SPDX narzędziem agent-bom dla agentów i serwerów MCP na maszynie, projektu, obrazu kontenera, repozytorium albo konta AWS, Azure czy GCP, wraz ze znanymi podatnościami. - 100sbom-analyzer
Analizuje SBOM pod kątem podatności i ryzyka dostawców: waliduje SBOM od dostawcy lub generuje go dla projektu wewnętrznego w CycloneDX i SPDX.