@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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 51 of 131)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 1 / 10 | |
| 8.0.1 | 1 / 10 | |
| 8.0.0 | 1 / 10 | |
| 7.0.8 | 1 / 10 | |
| 7.0.7 | 1 / 10 | |
| 7.0.6 | 1 / 10 | |
| 7.0.5 | 1 / 10 | |
| 7.0.4 | 1 / 10 | |
| 7.0.2 | 3 / 10 | |
| 7.0.1 | 3 / 10 | |
| 7.0.0 | 3 / 10 | |
| 6.1.4 | 3 / 10 | |
| 6.1.3 | 3 / 8 | |
| 6.1.1 | 3 / 8 | |
| 6.1.0 | 3 / 8 | |
| 6.0.10 | 3 / 8 | |
| 6.0.9 | 3 / 8 | |
| 6.0.8 | 3 / 8 | |
| 6.0.7 | 3 / 8 | |
| 6.0.6 | 3 / 9 | |
| 6.0.5 | 3 / 9 | |
| 6.0.4 | 3 / 9 | |
| 6.0.3 | 3 / 9 | |
| 6.0.2 | 3 / 9 | |
| 6.0.1 | 3 / 9 | |
| 6.0.0 | 3 / 9 | |
| 5.1.5 | 3 / 9 | |
| 5.1.4 | 3 / 9 | |
| 5.1.3 | 3 / 9 | |
| 5.1.2 | 3 / 9 | |
| 5.1.1 | 3 / 8 | |
| 5.1.0 | 3 / 10 | |
| 5.0.102 | 3 / 10 | |
| 5.0.101 | 3 / 10 | |
| 5.0.100 | 3 / 11 | |
| 5.0.99 | 3 / 33 | |
| 5.0.98 | 4 / 9 | |
| 5.0.97 | 4 / 9 | |
| 5.0.96 | 4 / 9 | |
| 5.0.95 | 4 / 10 | |
| 5.0.94 | 4 / 10 | |
| 5.0.93 | 4 / 10 | |
| 5.0.92 | 4 / 10 | |
| 5.0.91 | 4 / 7 | |
| 5.0.90 | 4 / 4 | |
| 5.0.89 | 4 / 4 | |
| 5.0.88 | 4 / 4 | |
| 5.0.87 | 4 / 4 | |
| 5.0.86 | 4 / 4 | |
| 5.0.84 | 4 / 4 | |
| 5.0.83 | 4 / 4 |
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-07, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-04, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.102
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-04, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.94
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.0.93
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.0.92
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.0.91
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.0.90
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.