@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 — 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 |
|---|---|---|---|---|
| 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 18 of 235)
| Version | Deps | Published |
|---|---|---|
| 1.16.18 | 8 / 9 | |
| 1.16.17 | 8 / 9 | |
| 1.16.16 | 8 / 9 | |
| 1.16.15 | 8 / 9 | |
| 1.16.14 | 8 / 9 | |
| 1.16.13 | 8 / 9 | |
| 1.16.12 | 8 / 9 | |
| 1.16.11 | 8 / 9 | |
| 1.16.3 | 9 / 9 | |
| 1.15.28 | 9 / 9 | |
| 1.15.25 | 9 / 9 | |
| 1.15.21 | 9 / 9 | |
| 1.15.15 | 9 / 9 | |
| 1.15.12 | 9 / 9 | |
| 1.15.10 | 9 / 9 | |
| 1.15.2 | 9 / 9 | |
| 1.14.3 | 9 / 9 | |
| 1.12.8 | 9 / 9 |
v1.16.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.