@xylabs/react-render-spin-check
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer, no behavioral risk. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react | AI (dependencies): Successor package per deprecation notice, same publisher family, expected migration dep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dep addition is the documented shim target, not an unrelated new dependency. | 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 / 8 | |
| 10.0.0 | 0 / 8 | |
| 9.1.2 | 0 / 8 | |
| 9.1.1 | 0 / 8 | |
| 9.1.0 | 0 / 8 | |
| 9.0.4 | 0 / 8 | |
| 9.0.3 | 0 / 8 | |
| 9.0.2 | 0 / 8 | |
| 9.0.1 | 0 / 8 | |
| 9.0.0 | 0 / 8 | |
| 8.0.4 | 0 / 8 | |
| 8.0.3 | 0 / 8 | |
| 8.0.2 | 0 / 8 | |
| 8.0.1 | 0 / 8 | |
| 8.0.0 | 0 / 8 | |
| 7.2.5 | 0 / 8 | |
| 7.2.4 | 0 / 8 | |
| 7.2.3 | 0 / 8 | |
| 7.2.2 | 0 / 8 | |
| 7.2.1 | 0 / 8 | |
| 7.2.0 | 0 / 8 | |
| 7.1.20 | 1 / 7 | |
| 7.1.17 | 0 / 7 | |
| 7.1.16 | 0 / 7 | |
| 7.1.15 | 0 / 7 | |
| 7.1.14 | 0 / 7 | |
| 7.1.13 | 0 / 7 | |
| 7.1.12 | 0 / 7 | |
| 7.1.11 | 0 / 7 | |
| 7.1.10 | 0 / 7 | |
| 7.1.9 | 0 / 7 |
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v8.0.0
2 findingsPackage 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-05-07, 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.
v7.1.20
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: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-04-07, but xyo 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.
v7.1.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-03-09, but xyo 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.
v7.1.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-01-28, but xyo 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.