← Home

@xylabs/sdk-react

35
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

joelbcarterjordantrouwrphansen91jonesmacatrouw

Keywords

utilitytypescriptreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ariestools/sdk-react AI (dependencies): Rename target of this deprecated shim, same maintainer/org lineage. ai
publish-pattern new-deps-added AI (publish-pattern): Expected: package deprecated in favor of this new dep. ai
provenance publisher-changed AI (provenance): xyo is the XY Labs org account with 3410 approved packages; org-account transition is expected for this package. ai
provenance no-provenance AI (provenance): Established XY Labs package; lack of provenance is consistent across their ecosystem and not a risk signal here. ai
license weak-copyleft-license:LGPL-3.0-only AI (license): LGPL-3.0-only is the declared license for this package across all versions; not a security concern. ai

Versions (showing 35 of 35)

Version Deps Published
11.0.0 1 / 26
10.0.5 1 / 26
10.0.3 1 / 25
10.0.2 1 / 25
10.0.1 0 / 52
10.0.0 25 / 27
9.1.2 25 / 27
9.1.1 25 / 27
9.1.0 25 / 27
9.0.4 25 / 33
9.0.3 25 / 33
9.0.2 26 / 32
9.0.1 26 / 34
9.0.0 26 / 37
8.0.4 26 / 37
8.0.3 26 / 37
8.0.2 26 / 38
8.0.1 26 / 38
8.0.0 25 / 36
7.2.5 25 / 36
7.2.4 25 / 36
7.2.3 25 / 36
7.2.2 25 / 36
7.2.1 25 / 37
7.2.0 25 / 37
7.1.20 25 / 18
7.1.17 25 / 11
7.1.16 25 / 11
7.1.15 25 / 11
7.1.14 25 / 11
7.1.13 25 / 11
7.1.12 25 / 11
7.1.11 25 / 10
7.1.10 25 / 10
7.1.9 25 / 28

v11.0.0

1 finding
INFO No provenance attestation provenance

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

v10.0.5

1 finding
INFO No provenance attestation provenance

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

v10.0.3

1 finding
INFO No provenance attestation provenance

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

v10.0.2

1 finding
INFO No provenance attestation provenance

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

v10.0.1

1 finding
INFO No provenance attestation provenance

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

v10.0.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: jonesmac → 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 (jonesmac) 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.