@dxos/messaging
Messaging
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dxos/edge-client | AI (dependencies): First-party DXOS monorepo package pinned to matching version; stable pattern across releases. | ai | |
| provenance | publisher-changed | AI (provenance): dxos-bot → GitHub Actions is a CI pipeline migration; SLSA attestation confirms integrity. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of yarolegovich aligns with the org-level CI migration; no malicious indicators present. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dep used via isomorphic-ws; phantom-dep heuristic fires but it's a legitimate dependency. | ai | |
| provenance | no-provenance | AI (provenance): DXOS monorepo consistently publishes without Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 15 / 3 | |
| 0.9.0 | 14 / 3 | |
| 0.8.3 | 14 / 3 | |
| 0.8.2 | 14 / 3 | |
| 0.8.1 | 14 / 3 | |
| 0.8.0 | 14 / 3 | |
| 0.7.4 | 14 / 3 | |
| 0.7.3 | 14 / 3 | |
| 0.7.2 | 14 / 3 | |
| 0.7.1 | 14 / 3 | |
| 0.7.0 | 14 / 3 | |
| 0.6.13 | 15 / 5 | |
| 0.6.12 | 15 / 5 | |
| 0.6.11 | 15 / 5 | |
| 0.6.10 | 15 / 5 | |
| 0.6.9 | 15 / 5 | |
| 0.6.8 | 15 / 5 | |
| 0.6.7 | 14 / 5 | |
| 0.6.6 | 14 / 5 | |
| 0.6.5 | 13 / 5 | |
| 0.6.4 | 13 / 5 | |
| 0.6.3 | 13 / 5 | |
| 0.6.2 | 13 / 5 | |
| 0.6.1 | 13 / 5 | |
| 0.6.0 | 13 / 5 | |
| 0.5.8 | 12 / 5 | |
| 0.5.7 | 12 / 5 | |
| 0.5.6 | 12 / 5 | |
| 0.5.5 | 12 / 5 | |
| 0.5.4 | 12 / 5 | |
| 0.5.3 | 12 / 5 | |
| 0.5.2 | 12 / 5 |
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.