@dxos/codec-protobuf
There's an associated @dxos/protobuf-compiler package that does codegen based on protobuf schema.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from dxos-bot to GitHub Actions CI is a documented org-level CI migration, backed by SLSA provenance attestation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer consistent with org moving to GitHub Actions-based publishing; no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): DXOS monorepo publishes via bot without Sigstore provenance consistently; stable pattern across versions. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 9 / 1 | |
| 0.9.0 | 9 / 1 | |
| 0.8.3 | 9 / 1 | |
| 0.8.2 | 9 / 1 | |
| 0.8.1 | 9 / 1 | |
| 0.8.0 | 9 / 1 | |
| 0.7.4 | 9 / 1 | |
| 0.7.3 | 9 / 1 | |
| 0.7.2 | 9 / 1 | |
| 0.7.1 | 9 / 1 | |
| 0.7.0 | 9 / 1 | |
| 0.6.13 | 9 / 1 | |
| 0.6.12 | 9 / 1 | |
| 0.6.11 | 9 / 1 | |
| 0.6.10 | 9 / 1 | |
| 0.6.9 | 9 / 1 | |
| 0.6.8 | 9 / 1 | |
| 0.6.7 | 9 / 1 | |
| 0.6.6 | 9 / 1 | |
| 0.6.5 | 9 / 1 | |
| 0.6.4 | 9 / 1 | |
| 0.6.3 | 9 / 1 | |
| 0.6.2 | 9 / 1 | |
| 0.6.1 | 9 / 1 | |
| 0.6.0 | 9 / 1 | |
| 0.5.8 | 9 / 1 | |
| 0.5.7 | 9 / 1 | |
| 0.5.6 | 9 / 1 | |
| 0.5.5 | 9 / 1 | |
| 0.5.4 | 9 / 1 | |
| 0.5.3 | 9 / 1 | |
| 0.5.2 | 9 / 1 |
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.