@xylabs/forget
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): High-volume publisher with clean track record; likely a CI environment change, not a supply-chain concern. | ai | |
| dependencies | unvetted-dep:@xylabs/delay | AI (dependencies): Sibling monorepo package from same publisher; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@xylabs/logger | AI (dependencies): Sibling monorepo package from same publisher; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@xylabs/typeof | AI (dependencies): Sibling monorepo package from same publisher; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@xylabs/promise | AI (dependencies): Sibling monorepo package from same publisher; version-locked to matching release. | 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.