@xyo-network/xl1-rpc
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata-only regression, no code/script changes; publisher has long clean track record. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Package deprecated as compatibility shim per package.json; stub is intentional. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package replacing removed ones, per deprecation notice. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email; confirmed legitimate publish. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer rotation within the same org; no evidence of hostile takeover. | ai | |
| phantom-deps | phantom-dep:@xylabs/arraybuffer | AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard Buffer.from base64 decode in a utility type file; no obfuscation or payload hiding. | ai | |
| phantom-deps | phantom-dep:@xylabs/exists | AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xyo-network/hash | AI (phantom-deps): Same-org dependency; heuristic false positive for this package. | ai | |
| dependencies | unvetted-peer-dep:@xyo-network/sdk-js | AI (dependencies): First-party peer dep from the same xyo-network org; stable pattern across versions. | ai | |
| dependencies | unvetted-peer-dep:@xylabs/sdk-js | AI (dependencies): First-party peer dep from the same xylabs org; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established xylabs org package; provenance absence is consistent across their published packages. | ai |
Versions (showing 51 of 522)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 1 / 28 | |
| 4.0.11 | 3 / 35 | |
| 4.0.10 | 3 / 35 | |
| 4.0.9 | 3 / 35 | |
| 4.0.8 | 3 / 34 | |
| 4.0.7 | 3 / 34 | |
| 4.0.6 | 3 / 33 | |
| 4.0.5 | 3 / 33 | |
| 4.0.4 | 3 / 33 | |
| 4.0.3 | 3 / 33 | |
| 4.0.2 | 3 / 33 | |
| 4.0.1 | 3 / 33 | |
| 4.0.0 | 3 / 33 | |
| 3.1.5 | 3 / 35 | |
| 3.1.4 | 3 / 35 | |
| 3.1.3 | 3 / 35 | |
| 3.1.2 | 3 / 35 | |
| 3.1.1 | 3 / 35 | |
| 3.1.0 | 3 / 35 | |
| 3.0.16 | 3 / 35 | |
| 3.0.15 | 3 / 35 | |
| 3.0.14 | 3 / 35 | |
| 3.0.13 | 3 / 35 | |
| 3.0.12 | 3 / 35 | |
| 3.0.11 | 3 / 35 | |
| 3.0.10 | 3 / 35 | |
| 3.0.9 | 3 / 35 | |
| 3.0.8 | 3 / 35 | |
| 3.0.7 | 3 / 35 | |
| 3.0.6 | 3 / 35 | |
| 3.0.5 | 3 / 35 | |
| 3.0.4 | 3 / 35 | |
| 3.0.3 | 3 / 35 | |
| 3.0.2 | 3 / 35 | |
| 3.0.1 | 3 / 35 | |
| 3.0.0 | 3 / 35 | |
| 2.2.3 | 3 / 35 | |
| 2.2.2 | 3 / 35 | |
| 2.2.1 | 3 / 35 | |
| 2.2.0 | 3 / 35 | |
| 2.1.9 | 3 / 36 | |
| 2.1.8 | 3 / 36 | |
| 2.1.7 | 3 / 36 | |
| 2.1.6 | 3 / 36 | |
| 2.1.5 | 3 / 36 | |
| 2.1.4 | 3 / 36 | |
| 2.1.3 | 3 / 38 | |
| 2.1.2 | 3 / 38 | |
| 2.1.1 | 3 / 38 | |
| 2.1.0 | 3 / 38 | |
| 2.0.14 | 3 / 38 |
v4.0.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jonesmac.
[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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joelbcarter.
[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
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joelbcarter.
[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 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joelbcarter.
[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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.