@xyo-network/xl1-wrappers
XYO Layer One SDK Wrappers
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 | missing-githead | AI (provenance): High-volume monorepo publisher; missing gitHead reflects CI env change, not tampering, given clean version diff. | ai |
Versions (showing 100 of 401)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 1 / 25 | |
| 4.0.11 | 3 / 30 | |
| 4.0.10 | 3 / 30 | |
| 4.0.9 | 3 / 30 | |
| 4.0.8 | 3 / 29 | |
| 4.0.7 | 3 / 29 | |
| 4.0.6 | 3 / 28 | |
| 4.0.5 | 3 / 28 | |
| 4.0.4 | 3 / 28 | |
| 4.0.3 | 3 / 28 | |
| 4.0.2 | 3 / 28 | |
| 4.0.1 | 3 / 28 | |
| 4.0.0 | 3 / 28 | |
| 3.1.5 | 3 / 30 | |
| 3.1.4 | 3 / 30 | |
| 3.1.3 | 3 / 30 | |
| 3.1.2 | 3 / 30 | |
| 3.1.1 | 3 / 30 | |
| 3.1.0 | 3 / 30 | |
| 3.0.16 | 3 / 30 | |
| 3.0.15 | 3 / 30 | |
| 3.0.14 | 3 / 30 | |
| 3.0.13 | 3 / 30 | |
| 3.0.12 | 3 / 30 | |
| 3.0.11 | 3 / 30 | |
| 3.0.10 | 3 / 30 | |
| 3.0.9 | 3 / 30 | |
| 3.0.8 | 3 / 30 | |
| 3.0.7 | 3 / 30 | |
| 3.0.6 | 3 / 30 | |
| 3.0.5 | 3 / 30 | |
| 3.0.4 | 3 / 30 | |
| 3.0.3 | 3 / 30 | |
| 3.0.2 | 3 / 30 | |
| 3.0.1 | 3 / 30 | |
| 3.0.0 | 3 / 30 | |
| 2.2.3 | 3 / 30 | |
| 2.2.2 | 3 / 30 | |
| 2.2.1 | 3 / 30 | |
| 2.2.0 | 3 / 30 | |
| 2.1.9 | 3 / 31 | |
| 2.1.8 | 3 / 31 | |
| 2.1.7 | 3 / 31 | |
| 2.1.6 | 3 / 31 | |
| 2.1.5 | 3 / 31 | |
| 2.1.4 | 3 / 31 | |
| 2.1.3 | 3 / 33 | |
| 2.1.2 | 3 / 33 | |
| 2.1.1 | 3 / 33 | |
| 2.1.0 | 3 / 33 | |
| 2.0.14 | 3 / 33 | |
| 2.0.13 | 3 / 33 | |
| 2.0.12 | 3 / 33 | |
| 2.0.11 | 3 / 33 | |
| 2.0.10 | 3 / 34 | |
| 2.0.9 | 3 / 34 | |
| 2.0.8 | 3 / 33 | |
| 2.0.7 | 3 / 33 | |
| 2.0.6 | 3 / 36 | |
| 2.0.5 | 3 / 54 | |
| 2.0.4 | 3 / 54 | |
| 2.0.3 | 3 / 54 | |
| 2.0.2 | 3 / 54 | |
| 2.0.1 | 3 / 54 | |
| 1.30.4 | 3 / 54 | |
| 1.26.48 | 3 / 57 | |
| 1.26.47 | 3 / 57 | |
| 1.26.46 | 3 / 57 | |
| 1.26.44 | 3 / 57 | |
| 1.26.43 | 3 / 57 | |
| 1.26.42 | 3 / 57 | |
| 1.26.39 | 3 / 57 | |
| 1.26.38 | 3 / 57 | |
| 1.26.37 | 3 / 66 | |
| 1.26.36 | 3 / 65 | |
| 1.26.35 | 3 / 65 | |
| 1.26.34 | 3 / 65 | |
| 1.26.33 | 3 / 65 | |
| 1.26.32 | 3 / 65 | |
| 1.26.31 | 3 / 65 | |
| 1.26.30 | 3 / 65 | |
| 1.26.29 | 3 / 65 | |
| 1.26.28 | 3 / 65 | |
| 1.26.27 | 3 / 64 | |
| 1.26.25 | 3 / 64 | |
| 1.26.24 | 3 / 65 | |
| 1.26.23 | 3 / 65 | |
| 1.26.19 | 3 / 65 | |
| 1.26.18 | 3 / 65 | |
| 1.26.17 | 3 / 65 | |
| 1.26.15 | 3 / 65 | |
| 1.26.14 | 3 / 24 | |
| 1.26.13 | 3 / 31 | |
| 1.26.12 | 3 / 14 | |
| 1.26.11 | 3 / 13 | |
| 1.26.10 | 3 / 13 | |
| 1.26.9 | 3 / 13 | |
| 1.26.8 | 3 / 13 | |
| 1.26.7 | 3 / 13 | |
| 1.26.6 | 3 / 13 |
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsPackage 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 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage 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 findingsPackage 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 findingsPackage 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 findingsPackage 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 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
2 findingsPackage 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.