@xyo-network/xl1-validation
XYO Layer One SDK Validation
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 from individual (jonesmac) to org account (xyo) is consistent with the package's xylabs/xyo-network org ownership. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw confirmed as known maintainer by email match on prior approved versions; not a new external actor. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer rotation within the same org (xylabs); no signs of hostile takeover. | ai | |
| provenance | no-provenance | AI (provenance): XYO Network packages consistently lack Sigstore provenance; stable false positive for this org. | ai |
Versions (showing 51 of 370)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 1 / 24 | |
| 4.0.11 | 2 / 28 | |
| 4.0.10 | 2 / 28 | |
| 4.0.9 | 2 / 28 | |
| 4.0.8 | 2 / 27 | |
| 4.0.7 | 2 / 27 | |
| 4.0.6 | 2 / 26 | |
| 4.0.5 | 2 / 26 | |
| 4.0.4 | 2 / 26 | |
| 4.0.3 | 2 / 26 | |
| 4.0.2 | 2 / 26 | |
| 4.0.1 | 2 / 26 | |
| 4.0.0 | 2 / 26 | |
| 3.1.5 | 2 / 28 | |
| 3.1.4 | 2 / 28 | |
| 3.1.3 | 2 / 28 | |
| 3.1.2 | 2 / 28 | |
| 3.1.1 | 2 / 28 | |
| 3.1.0 | 2 / 28 | |
| 3.0.16 | 2 / 28 | |
| 3.0.15 | 2 / 28 | |
| 3.0.14 | 2 / 28 | |
| 3.0.13 | 2 / 28 | |
| 3.0.12 | 2 / 28 | |
| 3.0.11 | 2 / 28 | |
| 3.0.10 | 2 / 28 | |
| 3.0.9 | 2 / 28 | |
| 3.0.8 | 2 / 28 | |
| 3.0.7 | 2 / 28 | |
| 3.0.6 | 2 / 28 | |
| 3.0.5 | 2 / 28 | |
| 3.0.4 | 2 / 28 | |
| 3.0.3 | 2 / 28 | |
| 3.0.2 | 2 / 28 | |
| 3.0.1 | 2 / 28 | |
| 3.0.0 | 2 / 28 | |
| 2.2.3 | 2 / 28 | |
| 2.2.2 | 2 / 28 | |
| 2.2.1 | 2 / 28 | |
| 2.2.0 | 2 / 28 | |
| 2.1.9 | 2 / 29 | |
| 2.1.8 | 2 / 29 | |
| 2.1.7 | 2 / 29 | |
| 2.1.6 | 2 / 29 | |
| 2.1.5 | 2 / 29 | |
| 2.1.4 | 2 / 29 | |
| 2.1.3 | 2 / 31 | |
| 2.1.2 | 2 / 31 | |
| 2.1.1 | 2 / 31 | |
| 2.1.0 | 2 / 31 | |
| 2.0.14 | 2 / 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.