@xyo-network/chain-reward-redemption
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xyo-network/chain-protocol | AI (phantom-deps): Same-org monorepo dependency; imported indirectly through other packages. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Monorepo workspace pattern; dependencies declared at root, imported indirectly. | ai | |
| phantom-deps | phantom-dep:@xyo-network/xl1-protocol | AI (phantom-deps): Same-org monorepo dependency; imported indirectly through other packages. | ai | |
| phantom-deps | phantom-dep:@xylabs/creatable | AI (phantom-deps): Config-referenced dependency in established monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:@xyo-network/typechain | AI (phantom-deps): Same-org scoped dependency; typical monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@xylabs/vitest-extended | AI (phantom-deps): Config-referenced test dependency in established monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Config-referenced dependency in established monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:mongodb | AI (phantom-deps): Config-referenced dependency in established monorepo; stable pattern. | ai | |
| provenance | no-provenance | AI (provenance): xyo-network packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 2 / 102 | |
| 2.0.0 | 2 / 102 | |
| 1.23.2 | 2 / 102 | |
| 1.23.0 | 2 / 102 | |
| 1.22.0 | 2 / 107 | |
| 1.21.3 | 2 / 102 | |
| 1.21.2 | 2 / 102 | |
| 1.21.0 | 2 / 102 | |
| 1.20.29 | 2 / 102 | |
| 1.20.28 | 2 / 102 | |
| 1.20.27 | 2 / 102 | |
| 1.20.25 | 14 / 73 | |
| 1.20.20 | 14 / 74 | |
| 1.20.19 | 14 / 74 | |
| 1.20.18 | 14 / 74 | |
| 1.20.17 | 14 / 74 | |
| 1.20.16 | 14 / 74 | |
| 1.20.15 | 13 / 25 | |
| 1.20.14 | 13 / 25 | |
| 1.20.13 | 13 / 25 | |
| 1.20.12 | 13 / 25 | |
| 1.20.11 | 13 / 25 | |
| 1.20.10 | 13 / 24 | |
| 1.20.9 | 13 / 24 | |
| 1.20.8 | 13 / 24 | |
| 1.20.5 | 19 / 38 | |
| 1.20.4 | 19 / 39 | |
| 1.20.3 | 19 / 39 | |
| 1.20.2 | 19 / 39 | |
| 1.20.1 | 19 / 39 | |
| 1.20.0 | 19 / 39 | |
| 1.19.18 | 19 / 39 | |
| 1.19.17 | 24 / 41 | |
| 1.19.16 | 24 / 42 | |
| 1.19.15 | 27 / 42 | |
| 1.19.14 | 32 / 37 | |
| 1.19.13 | 32 / 37 | |
| 1.19.12 | 32 / 37 | |
| 1.19.11 | 32 / 37 | |
| 1.19.10 | 32 / 37 | |
| 1.19.9 | 32 / 37 | |
| 1.19.8 | 32 / 37 | |
| 1.19.7 | 32 / 37 | |
| 1.19.6 | 32 / 37 | |
| 1.19.5 | 33 / 37 | |
| 1.19.4 | 33 / 37 | |
| 1.19.3 | 32 / 36 | |
| 1.19.2 | 32 / 36 | |
| 1.19.1 | 32 / 36 | |
| 1.19.0 | 32 / 36 | |
| 1.18.5 | 32 / 36 | |
| 1.18.4 | 32 / 36 | |
| 1.18.2 | 32 / 36 | |
| 1.18.1 | 32 / 36 | |
| 1.18.0 | 35 / 36 | |
| 1.17.7 | 35 / 36 | |
| 1.17.6 | 35 / 36 | |
| 1.17.2 | 35 / 36 | |
| 1.17.1 | 35 / 36 | |
| 1.17.0 | 35 / 36 | |
| 1.16.26 | 35 / 36 | |
| 1.16.24 | 35 / 36 | |
| 1.16.23 | 35 / 36 | |
| 1.16.22 | 35 / 36 | |
| 1.16.20 | 35 / 36 | |
| 1.16.19 | 35 / 36 | |
| 1.16.18 | 35 / 36 | |
| 1.16.15 | 35 / 36 | |
| 1.16.14 | 35 / 36 | |
| 1.16.13 | 35 / 36 | |
| 1.16.7 | 40 / 39 | |
| 1.16.4 | 41 / 39 | |
| 1.16.1 | 41 / 39 | |
| 1.16.0 | 41 / 39 | |
| 1.15.27 | 41 / 39 | |
| 1.15.26 | 41 / 39 | |
| 1.15.24 | 45 / 38 | |
| 1.15.23 | 45 / 38 | |
| 1.15.22 | 45 / 38 | |
| 1.15.21 | 44 / 38 | |
| 1.15.20 | 44 / 38 | |
| 1.15.19 | 44 / 38 | |
| 1.15.18 | 44 / 38 | |
| 1.15.17 | 44 / 38 | |
| 1.15.16 | 41 / 37 | |
| 1.15.15 | 41 / 37 | |
| 1.15.14 | 41 / 37 | |
| 1.15.13 | 41 / 37 | |
| 1.15.12 | 41 / 37 | |
| 1.15.11 | 41 / 37 | |
| 1.15.10 | 41 / 37 |
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.