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.

The tooling used to generate the SBOMs is sometimes over-inclusive, including dependencies only used for testing. The summaries here are generated via Go-aware tooling which includes fewer extra matches. We exclude Synadia Proprietary code from these summaries.

NATS

Control Plane

LicenseDependencies
Apache-2.0
109 dependencies
BSD-2-Clause
12 dependencies
BSD-3-Clause
72 dependencies
CC0-1.0
1 dependency
GNU-All-permissive-Copying-License
1 dependency
ISC
1 dependency
MIT
141 dependencies
MPL-2.0
7 dependencies
Unlicense
1 dependency

No external dependencies.

HTTP Gateway

Workloads

LicenseDependencies
Apache-2.0
16 dependencies
BSD-3-Clause
14 dependencies
MIT
28 dependencies

Connectors

LicenseDependencies
Apache-2.0
20 dependencies
BSD-2-Clause
2 dependencies
BSD-3-Clause
17 dependencies
ISC
1 dependency
MIT
24 dependencies
LicenseDependencies
Apache-2.0
115 dependencies
buf.build/gen/go/bufbuild/protovalidate/protocolbuffers/go/buf/validate
buf.build/gen/go/bufbuild/reflect/connectrpc/go/buf/reflect/v1beta1/reflectv1beta1connect
buf.build/gen/go/bufbuild/reflect/protocolbuffers/go/buf/reflect/v1beta1
BSD-2-Clause
22 dependencies
BSD-3-Clause
63 dependencies
BSL-1.0
1 dependency
EPL-2.0
1 dependency
GNU-All-permissive-Copying-License
2 dependencies
ISC
4 dependencies
LicenseRef-C-Ares
1 dependency
LicenseRef-MIT-Lucent
1 dependency
MIT
107 dependencies
MPL-2.0
8 dependencies
NCSA
1 dependency
OpenSSL
1 dependency
Zlib
1 dependency

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