cdx-proto
    Preparing search index...

    cdx-proto

    cdx-proto

    Runtime library to serialize/deserialize CycloneDX BOM with protocol buffers. The project was generated using protoc-gen-es from the official proto specification.

    • version-specific subpath exports: @cdxgen/cdx-proto/v1.5, v1.6, and v1.7
    • helper APIs for schema selection and BOM encode/decode workflows
    • leaner npm package contents that no longer publish generated docs/
    import {
    createBom,
    decodeBomBinary,
    encodeBomBinary,
    encodeBomJson,
    getBomSchema,
    parseBomJson,
    } from "@cdxgen/cdx-proto";
    import { BomSchema as BomSchema16 } from "@cdxgen/cdx-proto/v1.6";
    import { fromJson } from "@bufbuild/protobuf";

    // Use version-specific entrypoints when you only need one schema version.
    const bom16 = fromJson(BomSchema16, {
    specVersion: "1.6",
    version: 1,
    });

    // Or use the helper API to auto-select schemas and encode/decode BOMs.
    const bom = createBom("1.7", {
    version: 1,
    serialNumber: "urn:uuid:11111111-1111-1111-1111-111111111111",
    });

    const binary = encodeBomBinary(bom, {
    writeUnknownFields: true,
    });

    const decoded = decodeBomBinary("1.7", binary, {
    readUnknownFields: true,
    });

    const json = encodeBomJson(decoded, {
    alwaysEmitImplicit: true,
    });

    const parsed = parseBomJson({
    specVersion: "1.6",
    version: 1,
    });

    const schema = getBomSchema(parsed.specVersion);
    • getBomSchema(specVersion) returns the matching BomSchema for CycloneDX 1.5, 1.6, or 1.7.
    • createBom(specVersion, init) creates a BOM message and automatically sets specVersion.
    • parseBomJson(json) and parseBomJsonString(json) auto-detect the schema from specVersion / spec_version.
    • decodeBomBinary(specVersion, bytes) decodes a protobuf BOM when the schema version is known.
    • encodeBomBinary(bom), encodeBomJson(bom), and encodeBomJsonString(bom) choose the correct schema from the BOM itself.

    The helper layer is designed to work with canonical CycloneDX JSON rather than protobuf-flavored JSON.

    • parseBomJson() and decodeBomJson() accept canonical CycloneDX input such as:
      • root fields like bomFormat and specVersion
      • dashed aliases such as bom-ref, mime-type, and x-trust-boundary
      • canonical hash content fields like hashes[].content
      • canonical standards/declarations objects instead of protobuf list wrappers
    • Undefined object properties and undefined array entries are sanitized before protobuf parsing so callers can pass ordinary JavaScript objects without manually stripping undefined values first.
    • encodeBomJson() and encodeBomJsonString() restore canonical CycloneDX JSON on output, including:
      • bomFormat: "CycloneDX"
      • the BOM specVersion
      • canonical enum values instead of protobuf enum names such as CLASSIFICATION_*, HASH_ALG_*, or EXTERNAL_REFERENCE_TYPE_*
      • canonical object shapes for definitions and declarations
    • parseBomBinary() auto-detects the embedded supported schema version (1.5, 1.6, or 1.7) and can be paired with encodeBomJson() to read protobuf BOMs back as canonical CycloneDX JSON.

    In short: if you provide canonical CycloneDX JSON to the helper API, you should get canonical CycloneDX JSON back after binary or message round-trips.

    Use subpath exports to avoid loading schema versions you do not need:

    import { BomSchema as BomSchema15 } from "@cdxgen/cdx-proto/v1.5";
    import { BomSchema as BomSchema16 } from "@cdxgen/cdx-proto/v1.6";
    import { BomSchema as BomSchema17 } from "@cdxgen/cdx-proto/v1.7";

    MIT