@xyo-network/chain-sdk LGPL-3.0-only 12 versions

@xyo-network/chain-sdk

npm Repository Homepage

XYO Layer One SDK

12

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

atrouwjoelbcarterrphansen91jordantrouwjonesmac

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established xyo-network publisher; lack of provenance is consistent across their package ecosystem.	ai	2026/05/26
dependencies	unvetted-dep:@xyo-network/chain-rpc	AI (dependencies): Same-org monorepo sibling package, pinned to matching version; not an independent risk.	ai	2026/05/22
dependencies	unvetted-dep:@xyo-network/chain-viewers	AI (dependencies): Same-org monorepo sibling package, pinned to matching version; not an independent risk.	ai	2026/05/22

Versions (showing 12 of 12)

Version	Deps	Published
2.0.1	9 / 79	2026-05-21
2.0.0	9 / 79	2026-05-21
1.23.2	9 / 79	2026-05-14
1.23.0	9 / 79	2026-05-12
1.20.10	10 / 9	2026-03-26
1.20.8	10 / 9	2026-03-24
1.20.2	10 / 14	2026-03-09
1.16.19	11 / 14	2025-11-17
1.16.13	9 / 14	2025-11-15
1.16.12	9 / 14	2025-11-15
1.16.11	9 / 14	2025-11-15
1.16.10	9 / 16	2025-11-14

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.23.2

1 finding

LOW No provenance attestation provenance

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

v1.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.20.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.20.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.20.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.19

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

v1.16.12

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.