@xyo-network/xl1-network-model
XYO Layer One API
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): XYO Network org packages consistently trigger README link-dump signal; not indicative of spam for this publisher. | ai | |
| dependencies | unvetted-dep:@xyo-network/module-factory-locator | AI (dependencies): First-party @xyo-network org dependency; consistent with this package's ecosystem pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw confirmed as known maintainer matched by email on prior approved versions; not a new external actor. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removed but atrouw (known maintainer) took over; consistent with internal team rotation for xyo-network org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 320-version org package with consistent namespace; dormancy likely reflects project pause, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): XYO Network org packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 51 of 272)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 1 / 27 | |
| 4.0.11 | 1 / 29 | |
| 4.0.10 | 1 / 29 | |
| 4.0.9 | 1 / 29 | |
| 4.0.8 | 1 / 28 | |
| 4.0.7 | 1 / 28 | |
| 4.0.6 | 1 / 27 | |
| 4.0.5 | 1 / 27 | |
| 4.0.4 | 1 / 27 | |
| 4.0.3 | 1 / 27 | |
| 4.0.2 | 1 / 27 | |
| 4.0.1 | 1 / 27 | |
| 4.0.0 | 1 / 27 | |
| 3.1.5 | 1 / 29 | |
| 3.1.4 | 1 / 29 | |
| 3.1.3 | 1 / 29 | |
| 3.1.2 | 1 / 29 | |
| 3.1.1 | 1 / 29 | |
| 3.1.0 | 1 / 29 | |
| 3.0.16 | 1 / 29 | |
| 3.0.15 | 1 / 29 | |
| 3.0.14 | 1 / 29 | |
| 3.0.13 | 1 / 29 | |
| 3.0.12 | 1 / 29 | |
| 3.0.11 | 1 / 29 | |
| 3.0.10 | 1 / 29 | |
| 3.0.9 | 1 / 29 | |
| 3.0.8 | 1 / 29 | |
| 3.0.7 | 1 / 29 | |
| 3.0.6 | 1 / 29 | |
| 3.0.5 | 1 / 29 | |
| 3.0.4 | 1 / 29 | |
| 3.0.3 | 1 / 29 | |
| 3.0.2 | 1 / 29 | |
| 3.0.1 | 1 / 29 | |
| 3.0.0 | 1 / 29 | |
| 2.2.3 | 1 / 29 | |
| 2.2.2 | 1 / 29 | |
| 2.2.1 | 1 / 29 | |
| 2.2.0 | 1 / 29 | |
| 2.1.9 | 1 / 30 | |
| 2.1.8 | 1 / 30 | |
| 2.1.7 | 1 / 30 | |
| 2.1.6 | 1 / 30 | |
| 2.1.5 | 1 / 30 | |
| 2.1.4 | 1 / 30 | |
| 2.1.3 | 1 / 32 | |
| 2.1.2 | 1 / 32 | |
| 2.1.1 | 1 / 32 | |
| 2.1.0 | 1 / 32 | |
| 2.0.14 | 1 / 32 |
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.