@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 51 of 463)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 4 / 53 | |
| 1.26.41 | 4 / 57 | |
| 1.26.40 | 4 / 57 | |
| 1.26.38 | 4 / 57 | |
| 1.26.13 | 5 / 33 | |
| 1.26.12 | 5 / 17 | |
| 1.26.11 | 5 / 14 | |
| 1.26.10 | 5 / 14 | |
| 1.26.9 | 5 / 14 | |
| 1.26.8 | 5 / 14 | |
| 1.26.7 | 5 / 14 | |
| 1.26.6 | 5 / 14 | |
| 1.26.4 | 5 / 13 | |
| 1.26.3 | 5 / 13 | |
| 1.26.2 | 5 / 13 | |
| 1.26.1 | 5 / 13 | |
| 1.25.33 | 0 / 11 | |
| 1.25.32 | 0 / 11 | |
| 1.25.31 | 0 / 11 | |
| 1.25.30 | 0 / 11 | |
| 1.25.29 | 0 / 11 | |
| 1.25.28 | 0 / 11 | |
| 1.25.27 | 0 / 11 | |
| 1.25.26 | 0 / 11 | |
| 1.25.25 | 0 / 11 | |
| 1.25.24 | 0 / 11 | |
| 1.25.23 | 0 / 11 | |
| 1.25.22 | 0 / 11 | |
| 1.25.21 | 0 / 11 | |
| 1.25.20 | 0 / 11 | |
| 1.25.19 | 0 / 19 | |
| 1.25.18 | 0 / 19 | |
| 1.25.17 | 0 / 19 | |
| 1.25.16 | 0 / 19 | |
| 1.25.15 | 0 / 19 | |
| 1.25.14 | 0 / 19 | |
| 1.25.13 | 0 / 19 | |
| 1.25.12 | 0 / 19 | |
| 1.25.11 | 0 / 19 | |
| 1.25.10 | 0 / 19 | |
| 1.25.9 | 0 / 19 | |
| 1.25.8 | 0 / 19 | |
| 1.25.7 | 0 / 19 | |
| 1.25.6 | 0 / 19 | |
| 1.25.5 | 0 / 19 | |
| 1.25.4 | 0 / 19 | |
| 1.25.3 | 0 / 19 | |
| 1.25.2 | 0 / 19 | |
| 1.25.1 | 0 / 19 | |
| 1.25.0 | 0 / 19 | |
| 1.24.42 | 0 / 19 |
v2.0.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-05-26, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.26.41
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jonesmac.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.38
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.25
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.24
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.23
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.21
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.19
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.