@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 425)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 1 / 25 | |
| 4.0.11 | 5 / 32 | |
| 4.0.10 | 5 / 32 | |
| 4.0.9 | 5 / 32 | |
| 4.0.8 | 5 / 31 | |
| 4.0.7 | 5 / 31 | |
| 4.0.6 | 5 / 30 | |
| 4.0.5 | 5 / 30 | |
| 4.0.4 | 5 / 30 | |
| 4.0.3 | 5 / 30 | |
| 4.0.2 | 5 / 30 | |
| 4.0.1 | 5 / 30 | |
| 4.0.0 | 5 / 30 | |
| 3.1.5 | 5 / 32 | |
| 3.1.4 | 5 / 32 | |
| 3.1.3 | 5 / 32 | |
| 3.1.2 | 5 / 32 | |
| 3.1.1 | 5 / 32 | |
| 3.1.0 | 5 / 32 | |
| 3.0.16 | 5 / 32 | |
| 3.0.15 | 5 / 32 | |
| 3.0.14 | 5 / 32 | |
| 3.0.13 | 4 / 32 | |
| 3.0.12 | 4 / 32 | |
| 3.0.11 | 4 / 32 | |
| 3.0.10 | 4 / 32 | |
| 3.0.9 | 4 / 32 | |
| 3.0.8 | 4 / 32 | |
| 3.0.7 | 4 / 32 | |
| 3.0.6 | 4 / 32 | |
| 3.0.5 | 4 / 32 | |
| 3.0.4 | 4 / 32 | |
| 3.0.3 | 4 / 32 | |
| 3.0.2 | 4 / 32 | |
| 3.0.1 | 4 / 32 | |
| 3.0.0 | 4 / 32 | |
| 2.2.3 | 4 / 32 | |
| 2.2.2 | 4 / 32 | |
| 2.2.1 | 4 / 32 | |
| 2.2.0 | 4 / 32 | |
| 2.1.9 | 4 / 33 | |
| 2.1.8 | 4 / 33 | |
| 2.1.7 | 4 / 33 | |
| 2.1.6 | 4 / 33 | |
| 2.1.5 | 4 / 33 | |
| 2.1.4 | 4 / 33 | |
| 2.1.3 | 4 / 35 | |
| 2.1.2 | 4 / 35 | |
| 2.1.1 | 4 / 35 | |
| 2.1.0 | 4 / 35 | |
| 2.0.14 | 4 / 35 |
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
2 findingsPackage 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 (joelbcarter) on 2026-07-03, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsPackage 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-07-01, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (atrouw) on 2026-07-01, but jonesmac is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage 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 (joelbcarter) on 2026-06-30, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-07-03, but joelbcarter is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-06-30, but joelbcarter is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.3
2 findingsPackage 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 (joelbcarter) on 2026-06-30, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-06-29, but joelbcarter is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
2 findingsPackage 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 (joelbcarter) on 2026-06-29, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.