@ariestools/sdk-react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ariestools/sdk-react-number-status | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-motion | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-identicon | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-foundation | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-json-viewer | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-ui | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-core | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-crypto | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-analytics | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react-app | AI (dependencies): Same-org sibling package from monorepo split, not third-party. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 11.1.6 | 9 / 15 | |
| 11.1.5 | 9 / 18 | |
| 11.1.4 | 9 / 17 | |
| 11.1.3 | 9 / 17 | |
| 11.1.2 | 9 / 17 | |
| 11.1.1 | 9 / 17 | |
| 11.1.0 | 9 / 19 | |
| 11.0.3 | 4 / 19 | |
| 11.0.2 | 4 / 19 | |
| 11.0.1 | 4 / 19 | |
| 11.0.0 | 0 / 39 | |
| 10.0.5 | 0 / 39 | |
| 10.0.3 | 0 / 56 | |
| 10.0.2 | 0 / 56 |
v11.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.4
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-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.
v11.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
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-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.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.