@xyo-network/sdk-utils
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@xyo-network/witnesses | AI (dependencies): Same-org monorepo dep pinned to matching version; consistent with all other @xyo-network/* deps in this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK package in a large monorepo; sparse README/keywords are a style choice, not spam. | ai | |
| dependencies | unvetted-dep:@xyo-network/api | AI (dependencies): First-party sibling dep from same XYO monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/quadkey | AI (dependencies): First-party sibling dep from same XYO monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/api-models | AI (dependencies): First-party sibling dep from same XYO monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/schema-cache | AI (dependencies): First-party sibling dep from same XYO monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/metamask-connector | AI (dependencies): First-party sibling dep from same XYO monorepo; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established XYO Network package; provenance absence is consistent across all prior versions. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 6.0.9 | 8 / 34 | |
| 6.0.8 | 8 / 35 | |
| 6.0.7 | 8 / 35 | |
| 6.0.6 | 8 / 35 | |
| 6.0.5 | 8 / 39 | |
| 6.0.4 | 8 / 40 | |
| 6.0.3 | 8 / 40 | |
| 6.0.2 | 8 / 40 | |
| 6.0.1 | 8 / 40 | |
| 6.0.0 | 8 / 40 | |
| 5.6.3 | 8 / 40 | |
| 5.6.2 | 8 / 40 | |
| 5.5.2 | 8 / 43 | |
| 5.5.1 | 8 / 43 | |
| 5.5.0 | 8 / 68 | |
| 5.4.1 | 10 / 42 | |
| 5.4.0 | 11 / 42 | |
| 5.3.27 | 11 / 45 | |
| 5.3.20 | 11 / 30 | |
| 5.3.17 | 11 / 28 | |
| 5.3.8 | 11 / 6 | |
| 5.3.6 | 11 / 5 | |
| 5.3.5 | 9 / 4 | |
| 5.3.4 | 9 / 4 | |
| 5.3.1 | 9 / 3 | |
| 5.2.27 | 9 / 3 | |
| 5.2.17 | 9 / 3 | |
| 5.2.16 | 9 / 3 | |
| 5.2.14 | 9 / 3 | |
| 5.2.13 | 9 / 3 | |
| 5.2.11 | 9 / 3 | |
| 5.2.10 | 9 / 3 | |
| 5.2.9 | 9 / 3 | |
| 5.2.8 | 9 / 3 | |
| 5.2.5 | 9 / 3 | |
| 5.2.1 | 9 / 3 | |
| 5.1.22 | 9 / 3 | |
| 5.0.0 | 9 / 3 |
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.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.5.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.5.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.5.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.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.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.
v5.3.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.3.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.3.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.3.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.3.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.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.22
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.