@xylabs/delay
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): High-volume publisher (261 approved) with clean track record; dormancy pattern not indicative of takeover here. | ai | |
| provenance | no-provenance | AI (provenance): Established XY Labs package; lack of provenance is consistent across their entire SDK monorepo. | ai |
Versions (showing 10 of 111)
| Version | Deps | Published |
|---|---|---|
| 5.0.9 | 1 / 4 | |
| 5.0.8 | 1 / 4 | |
| 5.0.7 | 1 / 4 | |
| 5.0.6 | 1 / 4 | |
| 5.0.5 | 1 / 4 | |
| 5.0.4 | 1 / 4 | |
| 5.0.3 | 1 / 4 | |
| 5.0.2 | 1 / 4 | |
| 5.0.1 | 1 / 4 | |
| 5.0.0 | 1 / 4 |
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.