← Home

@xyo-network/xl1-rpc-server

npm Repository Homepage

XYO Layer One RPC HTTP Server

100
Versions
LGPL-3.0-only
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

atrouwjoelbcarterrphansen91jordantrouwjonesmac

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern rapid-publish AI (publish-pattern): Part of an active org release pipeline with 72 versions; rapid publish is consistent with automated CI releases. ai
provenance publisher-changed AI (provenance): Transition from individual (jonesmac) to org account (xyo) with 2783 approved packages; consistent with org-level publishing consolidation. ai
provenance missing-githead AI (provenance): Likely a CI/CD environment change; no other malicious signals present across this package's 43-version history. ai

Versions (showing 100 of 177)

Version Deps Published
4.6.4 1 / 7
4.6.3 1 / 7
4.6.2 1 / 7
4.6.1 1 / 7
4.6.0 1 / 7
4.5.3 1 / 7
4.5.2 1 / 7
4.5.1 1 / 7
4.5.0 1 / 7
4.4.10 1 / 7
4.4.9 1 / 7
4.4.8 1 / 7
4.4.7 1 / 7
4.4.6 1 / 7
4.4.5 1 / 7
4.4.4 1 / 7
4.4.3 1 / 7
4.4.2 1 / 7
4.4.1 1 / 7
4.4.0 1 / 7
4.3.3 1 / 7
4.3.2 1 / 7
4.3.1 1 / 7
4.3.0 1 / 7
4.2.3 1 / 7
4.2.2 1 / 7
4.2.1 1 / 7
4.2.0 1 / 7
4.1.6 1 / 7
4.1.5 1 / 7
4.1.4 1 / 7
4.1.3 1 / 7
4.1.2 1 / 7
4.1.1 1 / 7
4.1.0 1 / 7
4.0.18 1 / 7
4.0.17 1 / 7
4.0.16 1 / 7
4.0.15 1 / 7
4.0.14 1 / 7
4.0.12 1 / 7
4.0.11 0 / 8
4.0.10 0 / 8
4.0.9 0 / 8
4.0.8 0 / 8
4.0.7 0 / 8
4.0.6 0 / 8
4.0.5 0 / 8
4.0.4 0 / 8
4.0.3 0 / 8
4.0.2 0 / 8
4.0.1 0 / 8
4.0.0 0 / 8
3.1.5 0 / 8
3.1.4 0 / 8
3.1.3 0 / 8
3.1.2 0 / 8
3.1.1 0 / 8
3.1.0 0 / 8
3.0.16 0 / 8
3.0.15 0 / 8
3.0.14 0 / 8
3.0.13 0 / 8
3.0.12 0 / 8
3.0.11 0 / 8
3.0.10 0 / 8
3.0.9 0 / 8
3.0.8 0 / 8
3.0.7 0 / 8
3.0.6 0 / 8
3.0.5 0 / 8
3.0.4 0 / 8
3.0.3 0 / 8
3.0.2 0 / 8
3.0.1 0 / 8
3.0.0 0 / 8
2.2.3 0 / 8
2.2.2 0 / 8
2.2.1 0 / 8
2.2.0 0 / 8
2.1.9 0 / 8
2.1.8 0 / 8
2.1.7 0 / 8
2.1.6 0 / 8
2.1.5 0 / 8
2.1.4 0 / 8
2.1.3 0 / 8
2.1.2 0 / 8
2.1.1 0 / 8
2.1.0 0 / 8
2.0.14 0 / 8
2.0.13 0 / 8
2.0.12 0 / 8
2.0.11 0 / 8
2.0.10 0 / 8
2.0.9 0 / 8
2.0.8 0 / 8
2.0.7 0 / 8
2.0.6 0 / 8
2.0.5 0 / 8
Showing 100 of 177 Next page →

v4.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.10

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jonesmac → atrouw (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-17, 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.4.9

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jonesmac → atrouw (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-17, 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.4.8

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → jonesmac (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (jonesmac) than the most recent previously approved version (atrouw) on 2026-07-17, 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.4.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.6

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (joelbcarter) on 2026-07-16, 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.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → joelbcarter (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-07-16, 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.

v4.4.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (joelbcarter) on 2026-07-16, 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.4.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → joelbcarter (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-07-16, 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.

v4.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jonesmac → atrouw (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-15, 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.3.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → jonesmac (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (jonesmac) than the most recent previously approved version (atrouw) on 2026-07-15, 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.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (joelbcarter) on 2026-07-15, 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.2.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-07-14, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (joelbcarter) on 2026-07-14, 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.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → joelbcarter (on 2026-07-14, known maintainer) provenance

This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-07-14, 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.

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.8

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-07-03, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jonesmac → atrouw (on 2026-07-01, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → jonesmac (on 2026-07-01, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-06-30, known maintainer) provenance

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.

v4.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-06-30, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → joelbcarter (on 2026-07-03, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → joelbcarter (on 2026-06-30, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-06-30, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: atrouw → joelbcarter (on 2026-06-29, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.16

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: joelbcarter → atrouw (on 2026-06-29, known maintainer) provenance

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.