@dxos/schema
Common data types and utils.
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/echo-client | AI (dependencies): Same-org monorepo sibling published in lockstep; not third-party. | ai | |
| phantom-deps | phantom-dep:@dxos/async | AI (phantom-deps): Same-org scope, likely used indirectly via monorepo build. | ai | |
| dependencies | unvetted-dep:@dxos/echo | AI (dependencies): Same-org monorepo sibling dependency, pinned to matching version. | ai | |
| phantom-deps | phantom-dep:@dxos/echo-client | AI (phantom-deps): Same org scope (@dxos); phantom-dep heuristic unreliable for monorepo packages. | ai | |
| provenance | publisher-changed | AI (provenance): dxos-bot → GitHub Actions is a CI/CD migration; SLSA provenance attestation confirms official repo origin. | ai | |
| phantom-deps | phantom-dep:@dxos/client-protocol | AI (phantom-deps): Same org scope (@dxos); phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@dxos/debug | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are expected for internal DXOS packages. | ai | |
| phantom-deps | phantom-dep:@effect/schema | AI (phantom-deps): @effect/schema is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 13 / 7 | |
| 0.9.0 | 13 / 7 | |
| 0.8.3 | 19 / 8 | |
| 0.8.2 | 19 / 7 | |
| 0.8.1 | 16 / 5 | |
| 0.8.0 | 13 / 7 | |
| 0.7.4 | 14 / 6 | |
| 0.7.3 | 14 / 6 | |
| 0.7.2 | 13 / 6 | |
| 0.7.1 | 13 / 6 | |
| 0.7.0 | 13 / 6 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.