@xyo-network/xl1-protocol
XYO Layer One Protocol - All Protocol Packages
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; large approved track record confirms legitimacy. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removed as part of routine maintainer rotation within the same org; no takeover indicators. | ai | |
| provenance | publisher-changed | AI (provenance): joelbcarter is an established publisher (1813 approved) in the same org; transition appears legitimate. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard ArrayBuffer utility using Buffer.from for base64 decoding; not obfuscation. | ai | |
| dependencies | unvetted-dep:@xyo-network/module-events | AI (dependencies): Sibling package within the same @xyo-network org; stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): XYO Network org consistently uses link-dump READMEs and omits keywords; not indicative of spam or phishing for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with strong publisher track record; provenance gap is a process concern, not a security block. | ai |
Versions (showing 63 of 463)
| Version | Deps | Published |
|---|---|---|
| 1.4.36 | 13 / 13 | |
| 1.4.35 | 13 / 13 | |
| 1.4.34 | 13 / 13 | |
| 1.4.33 | 13 / 13 | |
| 1.4.32 | 13 / 13 | |
| 1.4.31 | 13 / 13 | |
| 1.4.30 | 13 / 13 | |
| 1.4.29 | 13 / 13 | |
| 1.4.28 | 13 / 13 | |
| 1.4.27 | 13 / 13 | |
| 1.4.26 | 13 / 13 | |
| 1.4.25 | 12 / 13 | |
| 1.4.24 | 12 / 13 | |
| 1.4.23 | 13 / 13 | |
| 1.4.22 | 13 / 13 | |
| 1.4.21 | 13 / 13 | |
| 1.4.20 | 13 / 13 | |
| 1.4.19 | 13 / 13 | |
| 1.4.18 | 13 / 13 | |
| 1.4.17 | 13 / 13 | |
| 1.4.16 | 13 / 13 | |
| 1.4.15 | 13 / 13 | |
| 1.4.14 | 13 / 13 | |
| 1.4.13 | 13 / 13 | |
| 1.4.12 | 13 / 13 | |
| 1.4.11 | 13 / 13 | |
| 1.4.10 | 13 / 13 | |
| 1.4.9 | 13 / 13 | |
| 1.4.8 | 13 / 13 | |
| 1.4.7 | 13 / 13 | |
| 1.4.6 | 13 / 13 | |
| 1.4.5 | 13 / 13 | |
| 1.4.4 | 13 / 17 | |
| 1.4.2 | 13 / 17 | |
| 1.4.1 | 13 / 17 | |
| 1.4.0 | 13 / 17 | |
| 1.3.42 | 13 / 17 | |
| 1.3.41 | 13 / 17 | |
| 1.3.40 | 13 / 17 | |
| 1.3.39 | 13 / 17 | |
| 1.3.38 | 13 / 17 | |
| 1.3.37 | 13 / 17 | |
| 1.3.36 | 13 / 17 | |
| 1.3.35 | 13 / 14 | |
| 1.3.34 | 13 / 14 | |
| 1.3.33 | 13 / 15 | |
| 1.3.32 | 13 / 15 | |
| 1.3.31 | 14 / 13 | |
| 1.3.30 | 14 / 13 | |
| 1.3.29 | 14 / 13 | |
| 1.3.28 | 14 / 13 | |
| 1.3.27 | 14 / 13 | |
| 1.3.26 | 14 / 13 | |
| 1.3.25 | 14 / 13 | |
| 1.3.24 | 14 / 13 | |
| 1.3.23 | 14 / 13 | |
| 1.3.22 | 14 / 14 | |
| 1.3.21 | 14 / 13 | |
| 1.3.20 | 14 / 16 | |
| 1.3.19 | 14 / 16 | |
| 1.3.18 | 14 / 16 | |
| 1.3.17 | 14 / 16 | |
| 1.3.13 | 15 / 16 |
v1.4.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.9
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
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.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.