@xyo-network/xl1-schema
XYO Layer One SDK Schema
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to org account 'xyo' with 1786 approved packages; consistent with org-level publishing consolidation. | ai | |
| provenance | missing-githead | AI (provenance): High-volume publisher with strong track record; single metadata gap in an otherwise clean, no-change release. | ai | |
| provenance | no-provenance | AI (provenance): XYO Network org packages consistently lack provenance; not a security signal for this publisher. | ai |
Versions (showing 51 of 421)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 1 / 24 | |
| 4.0.11 | 1 / 28 | |
| 4.0.10 | 1 / 28 | |
| 4.0.9 | 1 / 28 | |
| 4.0.8 | 1 / 27 | |
| 4.0.7 | 1 / 27 | |
| 4.0.6 | 1 / 26 | |
| 4.0.5 | 1 / 26 | |
| 4.0.4 | 1 / 26 | |
| 4.0.3 | 1 / 26 | |
| 4.0.2 | 1 / 26 | |
| 4.0.1 | 1 / 26 | |
| 4.0.0 | 1 / 26 | |
| 3.1.5 | 1 / 28 | |
| 3.1.4 | 1 / 28 | |
| 3.1.3 | 1 / 28 | |
| 3.1.2 | 1 / 28 | |
| 3.1.1 | 1 / 28 | |
| 3.1.0 | 1 / 28 | |
| 3.0.16 | 1 / 28 | |
| 3.0.15 | 1 / 28 | |
| 3.0.14 | 1 / 28 | |
| 3.0.13 | 1 / 28 | |
| 3.0.12 | 1 / 28 | |
| 3.0.11 | 1 / 28 | |
| 3.0.10 | 1 / 28 | |
| 3.0.9 | 1 / 28 | |
| 3.0.8 | 1 / 28 | |
| 3.0.7 | 1 / 28 | |
| 3.0.6 | 1 / 28 | |
| 3.0.5 | 1 / 28 | |
| 3.0.4 | 1 / 28 | |
| 3.0.3 | 1 / 28 | |
| 3.0.2 | 1 / 28 | |
| 3.0.1 | 1 / 28 | |
| 3.0.0 | 1 / 28 | |
| 2.2.3 | 1 / 28 | |
| 2.2.2 | 1 / 28 | |
| 2.2.1 | 1 / 28 | |
| 2.2.0 | 1 / 28 | |
| 2.1.9 | 1 / 29 | |
| 2.1.8 | 1 / 29 | |
| 2.1.7 | 1 / 29 | |
| 2.1.6 | 1 / 29 | |
| 2.1.5 | 1 / 29 | |
| 2.1.4 | 1 / 29 | |
| 2.1.3 | 1 / 31 | |
| 2.1.2 | 1 / 31 | |
| 2.1.1 | 1 / 31 | |
| 2.1.0 | 1 / 31 | |
| 2.0.14 | 1 / 31 |
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
2 findings[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 (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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findings[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-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 findings[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 (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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findings[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 (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 findings[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 (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 findings[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 (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 findings[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 (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 findings[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 (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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
2 findings[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 (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.