@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file-transition:dist/esm/index.js | AI (source-diff): Rollup-bundled barrel export file, not true obfuscation. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Framework-scoped convention-loaded package. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit runtime dependency. | ai | |
| 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 | |
| provenance | no-provenance | AI (provenance): Established package with public GitHub repo; lack of Sigstore attestation is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@junipero/hooks | AI (dependencies): Same-monorepo sibling dep from the same publisher; stable false positive for this package. | ai |
Versions (showing 75 of 75)
| 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.10.5 | 3 / 0 | |
| 3.10.4 | 3 / 0 | |
| 3.10.3 | 3 / 0 | |
| 3.10.1 | 3 / 0 | |
| 3.10.0 | 3 / 0 | |
| 3.9.1 | 3 / 0 | |
| 3.9.0 | 3 / 0 | |
| 3.8.1 | 3 / 0 | |
| 3.8.0 | 3 / 0 | |
| 3.7.4 | 3 / 0 | |
| 3.7.3 | 3 / 0 | |
| 3.7.2 | 3 / 0 | |
| 3.7.1 | 3 / 0 | |
| 3.7.0 | 3 / 0 | |
| 3.6.3 | 3 / 0 | |
| 3.6.2 | 3 / 0 | |
| 3.6.1 | 3 / 0 | |
| 3.6.0 | 3 / 0 | |
| 3.5.5 | 4 / 0 | |
| 3.5.4 | 4 / 0 | |
| 3.5.3 | 4 / 0 | |
| 3.5.1 | 4 / 0 | |
| 3.5.0 | 4 / 0 | |
| 3.4.14 | 5 / 0 | |
| 3.4.13 | 5 / 0 | |
| 3.4.11 | 5 / 0 | |
| 3.4.10 | 5 / 0 | |
| 3.4.9 | 5 / 0 | |
| 3.4.4 | 5 / 0 | |
| 3.4.3 | 5 / 0 | |
| 3.4.2 | 5 / 0 | |
| 3.4.1 | 5 / 0 | |
| 3.3.9 | 5 / 0 | |
| 3.3.8 | 5 / 0 | |
| 3.3.6 | 5 / 0 | |
| 3.3.5 | 5 / 0 | |
| 3.3.4 | 5 / 0 | |
| 3.3.3 | 5 / 0 | |
| 3.3.2 | 5 / 0 | |
| 3.3.1 | 5 / 0 | |
| 3.3.0 | 5 / 0 | |
| 3.2.4 | 5 / 0 | |
| 3.2.3 | 5 / 0 | |
| 3.2.2 | 5 / 0 | |
| 3.2.1 | 5 / 0 | |
| 3.2.0 | 4 / 0 | |
| 3.1.1 | 4 / 0 | |
| 3.1.0 | 4 / 0 | |
| 3.0.2 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 |
v3.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.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.4.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.4.13
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator. Artifact: bundled (rollup) — minified bundler output, not obfuscation on its own.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.