@xyo-network/xl1-rpc
XYO Layer One API
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email; confirmed legitimate publish. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer rotation within the same org; no evidence of hostile takeover. | ai | |
| phantom-deps | phantom-dep:@xylabs/exists | AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard Buffer.from base64 decode in a utility type file; no obfuscation or payload hiding. | ai | |
| phantom-deps | phantom-dep:@xyo-network/hash | AI (phantom-deps): Same-org dependency; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xylabs/arraybuffer | AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. | ai | |
| dependencies | unvetted-peer-dep:@xylabs/sdk-js | AI (dependencies): First-party peer dep from the same xylabs org; stable pattern across versions. | ai | |
| dependencies | unvetted-peer-dep:@xyo-network/sdk-js | AI (dependencies): First-party peer dep from the same xyo-network org; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established xylabs org package; provenance absence is consistent across their published packages. | ai |
Versions (showing 4 of 404)
| Version | Deps | Published |
|---|---|---|
| 1.2.12 | 17 / 10 | |
| 1.2.11 | 17 / 10 | |
| 1.2.10 | 18 / 8 | |
| 1.2.9 | 18 / 8 |
v1.2.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.
v1.2.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.
v1.2.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.
v1.2.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.