@junipero/react
🏔 Junipero Design System React components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher identity matches package author; 138-version history and unchanged content make takeover unlikely. | ai | |
| dependencies | unvetted-dep:@junipero/core | AI (dependencies): Same-monorepo sibling dep from the same publisher; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@junipero/hooks | AI (dependencies): Same-monorepo sibling dep from the same publisher; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with public GitHub repo; lack of Sigstore attestation is common and not a risk signal here. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 4 / 0 | |
| 3.12.22 | 4 / 0 | |
| 3.12.20 | 4 / 0 | |
| 3.12.19 | 4 / 0 | |
| 3.12.18 | 4 / 0 | |
| 3.12.17 | 3 / 0 | |
| 3.12.16 | 3 / 0 | |
| 3.12.14 | 3 / 0 | |
| 3.12.13 | 3 / 0 | |
| 3.12.12 | 3 / 0 | |
| 3.12.11 | 3 / 0 | |
| 3.12.10 | 3 / 0 | |
| 3.12.9 | 3 / 0 | |
| 3.12.8 | 3 / 0 | |
| 3.12.7 | 3 / 0 | |
| 3.12.6 | 3 / 0 | |
| 3.12.5 | 3 / 0 | |
| 3.12.4 | 3 / 0 | |
| 3.12.3 | 3 / 0 | |
| 3.12.1 | 3 / 0 | |
| 3.12.0 | 3 / 0 | |
| 3.11.0 | 3 / 0 | |
| 3.10.7 | 3 / 0 | |
| 3.10.6 | 3 / 0 | |
| 3.9.1 | 3 / 0 |
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.