@xylabs/base
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Large established publisher (1984 approved pkgs); likely CI environment change, not a supply-chain indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @opentelemetry/api is a well-established CNCF library; not a suspicious dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established XYO Labs package; no provenance is consistent across all 233 versions. | ai | |
| dependencies | unvetted-dep:@xylabs/assert | AI (dependencies): Same-org sibling dep from XYLabs monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xylabs/logger | AI (dependencies): Same-org sibling dep from XYLabs monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xylabs/object | AI (dependencies): Same-org sibling dep from XYLabs monorepo; co-released at matching version. | ai |
Versions (showing 11 of 116)
| Version | Deps | Published |
|---|---|---|
| 5.0.10 | 4 / 4 | |
| 5.0.9 | 4 / 4 | |
| 5.0.8 | 4 / 4 | |
| 5.0.7 | 4 / 4 | |
| 5.0.6 | 4 / 4 | |
| 5.0.5 | 4 / 4 | |
| 5.0.4 | 4 / 4 | |
| 5.0.3 | 4 / 4 | |
| 5.0.2 | 4 / 4 | |
| 5.0.1 | 4 / 4 | |
| 5.0.0 | 4 / 4 |
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.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.
v5.0.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.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.