@xyo-network/react-sdk No license 40 versions

@xyo-network/react-sdk

npm Repository Homepage

40

Versions

—

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

Keywords

xyoutilitytypescriptreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@xyo-network/react-os	AI (dependencies): First-party sibling package in same monorepo, pinned to identical version.	ai	2026/07/19
dependencies	unvetted-dep:@xyo-network/react-form	AI (dependencies): First-party sibling package in same monorepo, pinned to identical version.	ai	2026/07/19
dependencies	unvetted-dep:@xyo-network/react-footer	AI (dependencies): First-party sibling package in same monorepo, pinned to identical version.	ai	2026/07/19
dependencies	unvetted-dep:@xyo-network/payload-viewer-protocol	AI (dependencies): First-party XYO monorepo sibling package, same publisher/org.	ai	2026/07/19
publish-pattern	new-deps-added	AI (publish-pattern): Feature expansion adding first-party and well-known ecosystem deps, no scripts/exfil.	ai	2026/07/19

Versions (showing 40 of 40)

Version	Deps	Published
10.6.0	18 / 31	2026/07/25
10.5.0	20 / 33	2026-07-19
10.3.0	0 / 51	2026-07-15
10.2.3	0 / 52	2026-07-15
10.2.2	0 / 52	2026-07-14
10.2.1	0 / 52	2026-07-14
10.2.0	0 / 52	2026-07-14
10.1.0	0 / 52	2026-07-13
10.0.12	0 / 89	2026-07-11
10.0.11	0 / 89	2026-07-10
10.0.10	0 / 89	2026-07-09
10.0.9	0 / 79	2026-07-07
10.0.8	0 / 79	2026-07-07
10.0.7	0 / 79	2026-07-07
10.0.6	0 / 98	2026-07-07
10.0.5	32 / 64	2026-07-07
10.0.4	32 / 63	2026-07-04
10.0.3	32 / 136	2026-06-30
10.0.2	32 / 138	2026-06-24
10.0.0	32 / 138	2026-06-24
9.1.1	32 / 138	2026-06-13
9.1.0	32 / 138	2026-06-11
9.0.6	32 / 142	2026-06-08
9.0.5	32 / 142	2026-06-05
9.0.4	32 / 141	2026-06-03
9.0.2	32 / 174	2026-06-02
9.0.1	32 / 185	2026-06-01
9.0.0	32 / 188	2026-05-20
8.0.1	32 / 188	2026-05-16
8.0.0	32 / 189	2026-05-08
7.6.3	32 / 188	2026-05-07
7.6.2	32 / 190	2026-05-06
7.6.1	32 / 190	2026-05-05
7.5.12	32 / 188	2026-04-23
7.5.11	32 / 192	2026-04-23
7.5.6	32 / 16	2026-03-27
7.5.3	32 / 15	2026-02-13
7.5.2	32 / 15	2026-02-12
7.5.1	32 / 15	2026-02-11
7.5.0	32 / 14	2026-01-28

v10.6.0

1 finding

LOW No provenance attestation provenance

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

v10.5.0

1 finding

LOW No provenance attestation provenance

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

v10.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: 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.

v10.2.3

1 finding

LOW No provenance attestation provenance

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

v10.2.2

1 finding

LOW No provenance attestation provenance

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

v10.2.1

1 finding

LOW No provenance attestation provenance

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

v10.2.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: atrouw → jonesmac (on 2026-07-14, known maintainer) provenance

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

v10.1.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: jonesmac → atrouw (on 2026-07-13, known maintainer) provenance

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

v10.0.12

1 finding

LOW No provenance attestation provenance

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

v10.0.11

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-10, known maintainer) provenance

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

v10.0.10

1 finding

LOW No provenance attestation provenance

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

v10.0.9

1 finding

LOW No provenance attestation provenance

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

v10.0.8

1 finding

LOW No provenance attestation provenance

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

v10.0.7

1 finding

LOW No provenance attestation provenance

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

v10.0.6

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.

v10.0.5

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.

v10.0.4

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.

v10.0.3

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.

v10.0.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.

v10.0.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.

v9.1.1

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.

v9.1.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.

v9.0.6

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.

v9.0.5

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.

v9.0.4

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.

v9.0.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.

v9.0.1

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.

v9.0.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.

v8.0.1

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.

v8.0.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.

v7.6.3

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.

v7.6.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.

v7.6.1

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.

v7.5.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.

v7.5.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.

v7.5.6

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.

v7.5.3

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.

v7.5.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.

v7.5.1

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.

v7.5.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.