Synadia Platform

Software Bill of Materials

What is it?

The Software Bill of Materials (SBOM) is an inventory of components used in building Synadia Platform. The SBOM provides transparency into software dependencies, including versions and licensing, and allows for easier compliance and vulnerability identification.

Each platform component publishes its SBOM in the SPDX format as a release asset in the linked repository. For a simpler view, each component below includes a table of all the dependencies for a build of the current release.

NATS

Control Plane

LicenseDependencies
Apache-2.0
149 dependencies
BSD-2-Clause
10 dependencies
BSD-2-Clause-Views
2 dependencies
BSD-3-Clause
82 dependencies
CC-BY-SA-4.0
1 dependency
CC0-1.0
1 dependency
ISC
1 dependency
MIT
167 dependencies
MPL-2.0
6 dependencies
Unlicense
1 dependency

No external dependencies.

HTTP Gateway

LicenseDependencies
Apache-2.0
14 dependencies
BSD-2-Clause
1 dependency
BSD-3-Clause
12 dependencies
MIT
25 dependencies
Proprietary
1 dependency
Unlicense
1 dependency

Workloads

LicenseDependencies
Apache-2.0
88 dependencies
BSD-2-Clause
5 dependencies
BSD-3-Clause
40 dependencies
CC-BY-SA-4.0
1 dependency
ISC
1 dependency
MIT
50 dependencies
MPL-2.0
4 dependencies
Proprietary
1 dependency
Unlicense
1 dependency

Connectors

LicenseDependencies
Apache-2.0
22 dependencies
BSD-2-Clause
2 dependencies
BSD-3-Clause
17 dependencies
ISC
1 dependency
MIT
26 dependencies
Proprietary
1 dependency
LicenseDependencies
Apache-2.0
165 dependencies
BSD-2-Clause
23 dependencies
BSD-2-Clause-Views
1 dependency
BSD-3-Clause
77 dependencies
BSL-1.0
2 dependencies
CC-BY-3.0
2 dependencies
CC0-1.0
1 dependency
EPL-2.0
1 dependency
HPND
2 dependencies
ISC
5 dependencies
MIT
131 dependencies
MIT-0
1 dependency
MPL-2.0
9 dependencies
NCSA
2 dependencies
OpenSSL
2 dependencies
Zlib
2 dependencies

Schema Registry

Signed Attestation

Currently, only the control-plane OCI images are signed. This is being rolled out for the rest of the components.

For components distributed as OCI images, attestations are signed by a Synadia key to allow for verification of authenticity. This can be validated using Sigstore Cosign.

Signature Verification:

cosign verify-attestation \
    --certificate-identity-regexp '^https://github.com/ConnectEverything' \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    registry.synadia.io/<component> > /dev/null

Replace <component> with the component name (e.g., control-plane, http-gateway).

In the above command, we redirected STDOUT to /dev/null because it contains the complete SBOM as base64-encoded JSON. We are able to decode this if we want to see the SBOM itself.

cosign verify-attestation \
    --certificate-identity-regexp '^https://github.com/ConnectEverything' \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    registry.synadia.io/<component> \
    | jq -r '.payload' | base64 -d | jq '.predicate.Data | fromjson'
Previous
Deleting a Schema