@xyo-network/xl1-protocol-lib
XYO Layer One 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual (jonesmac) to org account (xyo) is consistent with the XY Labs org; xyo has extensive approved publishing history. | ai | |
| provenance | missing-githead | AI (provenance): Likely CI/CD environment change; no other malicious indicators; package otherwise consistent with established org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established xylabs org package; README style is consistent across their ecosystem, not a phishing indicator. | ai | |
| provenance | no-provenance | AI (provenance): XYO Network org package; provenance absence is common and no other risk signals present. | ai |
Versions (showing 100 of 130)
| 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 | |
| 2.0.13 | 1 / 31 | |
| 2.0.12 | 1 / 31 | |
| 2.0.11 | 1 / 31 | |
| 2.0.10 | 1 / 32 | |
| 2.0.9 | 1 / 32 | |
| 2.0.8 | 1 / 31 | |
| 2.0.7 | 1 / 31 | |
| 2.0.6 | 1 / 34 | |
| 2.0.5 | 1 / 51 | |
| 2.0.4 | 1 / 51 | |
| 2.0.3 | 1 / 51 | |
| 2.0.2 | 1 / 51 | |
| 2.0.1 | 1 / 51 | |
| 2.0.0 | 1 / 51 | |
| 1.30.4 | 1 / 51 | |
| 1.30.3 | 1 / 51 | |
| 1.30.2 | 1 / 51 | |
| 1.30.1 | 1 / 51 | |
| 1.30.0 | 1 / 51 | |
| 1.29.8 | 1 / 51 | |
| 1.29.7 | 1 / 51 | |
| 1.29.6 | 1 / 51 | |
| 1.29.5 | 1 / 51 | |
| 1.29.4 | 1 / 51 | |
| 1.29.3 | 1 / 51 | |
| 1.29.2 | 1 / 51 | |
| 1.29.0 | 1 / 51 | |
| 1.28.6 | 1 / 51 | |
| 1.28.5 | 1 / 51 | |
| 1.28.4 | 1 / 51 | |
| 1.28.3 | 1 / 51 | |
| 1.28.2 | 1 / 51 | |
| 1.28.0 | 1 / 51 | |
| 1.27.1 | 1 / 51 | |
| 1.27.0 | 1 / 54 | |
| 1.26.49 | 1 / 55 | |
| 1.26.48 | 1 / 55 | |
| 1.26.47 | 1 / 55 | |
| 1.26.46 | 1 / 55 | |
| 1.26.44 | 1 / 55 | |
| 1.26.43 | 1 / 55 | |
| 1.26.42 | 1 / 55 | |
| 1.26.41 | 1 / 55 | |
| 1.26.40 | 1 / 55 | |
| 1.26.39 | 1 / 55 | |
| 1.26.38 | 1 / 55 | |
| 1.26.37 | 1 / 64 | |
| 1.26.36 | 2 / 62 | |
| 1.26.35 | 2 / 62 |
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.