@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, 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer atrouw matched to known maintainer email on prior versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org account rotation, not a takeover; corroborated by provenance INFO note. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer, no deps/scripts changed. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is the package's own documented successor per deprecation notice, not an unvetted third party. | ai | |
| 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 31 of 131)
| Version | Deps | Published |
|---|---|---|
| 5.0.30 | 1 / 4 | |
| 5.0.29 | 1 / 4 | |
| 5.0.28 | 1 / 4 | |
| 5.0.27 | 1 / 4 | |
| 5.0.26 | 1 / 4 | |
| 5.0.25 | 1 / 4 | |
| 5.0.24 | 1 / 4 | |
| 5.0.23 | 1 / 4 | |
| 5.0.22 | 1 / 4 | |
| 5.0.21 | 1 / 4 | |
| 5.0.20 | 1 / 4 | |
| 5.0.19 | 1 / 4 | |
| 5.0.18 | 1 / 4 | |
| 5.0.17 | 1 / 4 | |
| 5.0.16 | 1 / 4 | |
| 5.0.15 | 1 / 4 | |
| 5.0.14 | 1 / 4 | |
| 5.0.13 | 1 / 4 | |
| 5.0.12 | 1 / 4 | |
| 5.0.11 | 1 / 4 | |
| 5.0.10 | 1 / 4 | |
| 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.30
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.29
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.28
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.27
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.26
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.25
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.24
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.23
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.22
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.21
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.20
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.19
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.18
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.17
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.16
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.15
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.14
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.13
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.12
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.11
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.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.