@xyo-network/xl1-protocol-sdk
XYO Layer One SDK Protocol
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/typechain | AI (phantom-deps): Same-org dep declared in package.json; likely used transitively or in type generation, stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard cross-environment base64 decode utility; no obfuscation or payload delivery context. | ai | |
| phantom-deps | phantom-dep:@xyo-network/archivist-memory | AI (phantom-deps): Same-org dep declared for transitive/peer use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xyo-network/id-payload-plugin | AI (phantom-deps): Same-org dep declared for transitive/peer use; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/xl1-driver-memory | AI (dependencies): Same-org sibling package from XYO Network; consistent versioning pattern across the xl1 ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to org account 'xyo' with strong track record; consistent with legitimate maintainer consolidation for this established package. | ai | |
| provenance | missing-githead | AI (provenance): High-volume publisher with strong approval history; single missing gitHead in an otherwise clean incremental release is low risk for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established org package with 432 versions and clean diff; dormancy likely reflects development cycle, not takeover. | ai | |
| phantom-deps | phantom-dep:@xyo-network/xl1-schema | AI (phantom-deps): Same-org sibling package; declared as dep and likely re-exported rather than directly imported. | ai |
Versions (showing 88 of 390)
| Version | Deps | Published |
|---|---|---|
| 1.7.11 | 16 / 6 | |
| 1.7.10 | 16 / 6 | |
| 1.7.9 | 16 / 6 | |
| 1.7.8 | 16 / 6 | |
| 1.7.7 | 16 / 6 | |
| 1.7.6 | 16 / 6 | |
| 1.7.5 | 14 / 6 | |
| 1.7.4 | 14 / 6 | |
| 1.7.3 | 14 / 6 | |
| 1.7.2 | 14 / 6 | |
| 1.7.1 | 14 / 6 | |
| 1.7.0 | 14 / 6 | |
| 1.6.6 | 14 / 6 | |
| 1.6.5 | 14 / 6 | |
| 1.6.4 | 14 / 6 | |
| 1.6.3 | 14 / 6 | |
| 1.6.2 | 14 / 6 | |
| 1.6.1 | 13 / 6 | |
| 1.6.0 | 13 / 6 | |
| 1.5.37 | 13 / 6 | |
| 1.5.36 | 13 / 6 | |
| 1.5.35 | 13 / 6 | |
| 1.5.34 | 13 / 6 | |
| 1.5.33 | 13 / 6 | |
| 1.5.32 | 13 / 6 | |
| 1.5.31 | 13 / 6 | |
| 1.5.30 | 13 / 6 | |
| 1.5.29 | 11 / 5 | |
| 1.5.28 | 11 / 5 | |
| 1.5.27 | 11 / 5 | |
| 1.5.26 | 11 / 5 | |
| 1.5.25 | 11 / 5 | |
| 1.5.24 | 11 / 5 | |
| 1.5.23 | 11 / 5 | |
| 1.5.22 | 11 / 5 | |
| 1.5.21 | 11 / 5 | |
| 1.5.20 | 11 / 5 | |
| 1.5.19 | 11 / 5 | |
| 1.5.18 | 11 / 5 | |
| 1.5.17 | 11 / 5 | |
| 1.5.16 | 11 / 5 | |
| 1.5.15 | 11 / 5 | |
| 1.5.14 | 11 / 5 | |
| 1.5.13 | 11 / 5 | |
| 1.5.12 | 11 / 5 | |
| 1.5.11 | 11 / 5 | |
| 1.5.10 | 11 / 5 | |
| 1.5.9 | 11 / 5 | |
| 1.5.8 | 11 / 5 | |
| 1.5.7 | 11 / 5 | |
| 1.5.6 | 11 / 5 | |
| 1.5.5 | 11 / 5 | |
| 1.5.4 | 11 / 5 | |
| 1.5.3 | 11 / 5 | |
| 1.5.2 | 11 / 5 | |
| 1.5.1 | 11 / 5 | |
| 1.5.0 | 11 / 5 | |
| 1.4.8 | 11 / 5 | |
| 1.4.7 | 11 / 5 | |
| 1.4.6 | 11 / 5 | |
| 1.4.5 | 11 / 5 | |
| 1.4.4 | 11 / 5 | |
| 1.4.3 | 11 / 5 | |
| 1.4.2 | 11 / 5 | |
| 1.4.0 | 11 / 5 | |
| 1.3.31 | 11 / 5 | |
| 1.3.30 | 11 / 5 | |
| 1.3.29 | 11 / 5 | |
| 1.3.28 | 11 / 5 | |
| 1.3.27 | 11 / 6 | |
| 1.3.26 | 11 / 6 | |
| 1.3.25 | 11 / 6 | |
| 1.3.24 | 11 / 6 | |
| 1.3.23 | 11 / 6 | |
| 1.3.22 | 11 / 6 | |
| 1.3.21 | 11 / 6 | |
| 1.3.20 | 11 / 6 | |
| 1.3.19 | 11 / 6 | |
| 1.3.18 | 11 / 6 | |
| 1.3.17 | 11 / 6 | |
| 1.3.16 | 11 / 6 | |
| 1.3.15 | 11 / 6 | |
| 1.3.14 | 11 / 6 | |
| 1.3.13 | 8 / 6 | |
| 1.3.12 | 8 / 6 | |
| 1.3.11 | 8 / 6 | |
| 1.3.10 | 8 / 6 | |
| 1.3.9 | 8 / 6 |
v1.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.