@xylabs/assert
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Dep is the package's own documented deprecation-successor (@ariestools/sdk), not a random third-party add. | ai | |
| provenance | missing-githead | AI (provenance): Publisher has 223 approved packages; likely a CI/build environment change in the monorepo, not a takeover signal. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher xyo has 210 approved packages and 0 rejections; dormancy likely reflects org release cadence, not takeover. | ai |
Versions (showing 31 of 131)
| Version | Deps | Published |
|---|---|---|
| 5.0.30 | 0 / 3 | |
| 5.0.29 | 0 / 3 | |
| 5.0.28 | 0 / 3 | |
| 5.0.27 | 0 / 3 | |
| 5.0.26 | 0 / 3 | |
| 5.0.25 | 0 / 3 | |
| 5.0.24 | 0 / 3 | |
| 5.0.23 | 0 / 3 | |
| 5.0.22 | 0 / 3 | |
| 5.0.21 | 0 / 3 | |
| 5.0.20 | 0 / 3 | |
| 5.0.19 | 0 / 3 | |
| 5.0.18 | 0 / 3 | |
| 5.0.17 | 0 / 3 | |
| 5.0.16 | 0 / 3 | |
| 5.0.15 | 0 / 3 | |
| 5.0.14 | 0 / 3 | |
| 5.0.13 | 0 / 3 | |
| 5.0.12 | 0 / 3 | |
| 5.0.11 | 0 / 3 | |
| 5.0.10 | 0 / 3 | |
| 5.0.9 | 0 / 3 | |
| 5.0.8 | 0 / 3 | |
| 5.0.7 | 0 / 3 | |
| 5.0.6 | 0 / 3 | |
| 5.0.5 | 0 / 3 | |
| 5.0.4 | 0 / 3 | |
| 5.0.3 | 0 / 3 | |
| 5.0.2 | 0 / 3 | |
| 5.0.1 | 0 / 3 | |
| 5.0.0 | 0 / 3 |
v5.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.