@auth0/auth0-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Large version gap in diff baseline (v2.1.0→v2.16.1); size growth is accumulated features. | ai | |
| source-diff | encoded-string-file:dist/auth0-react.min.js | AI (source-diff): Standard rollup-minified JS output; stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Migration to GitHub Actions CI/CD with SLSA provenance; expected for Auth0 org. | ai | |
| source-diff | encoded-string-file:dist/auth0-react.cjs.js | AI (source-diff): Standard rollup-minified JS output; stable for this package. | ai | |
| source-diff | encoded-string-file:dist/auth0-react.esm.js | AI (source-diff): Standard rollup-minified JS output; stable for this package. | ai | |
| source-diff | encoded-string-file:dist/auth0-react.js | AI (source-diff): Standard rollup-minified JS output; stable for this package. | ai | |
| dependencies | unvetted-dep:@auth0/auth0-spa-js | AI (dependencies): @auth0/auth0-spa-js is Auth0's own first-party SPA SDK; stable dependency for this package across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Auth0 org package with 1.1M weekly downloads; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.16.2 | 1 / 37 | |
| 2.16.1 | 1 / 38 | |
| 2.16.0 | 1 / 38 | |
| 2.15.1 | 1 / 38 | |
| 2.15.0 | 1 / 38 | |
| 2.14.0 | 1 / 38 | |
| 2.13.0 | 1 / 38 | |
| 2.12.0 | 1 / 38 | |
| 2.11.0 | 1 / 38 | |
| 2.10.0 | 1 / 38 | |
| 2.9.0 | 1 / 38 | |
| 2.8.0 | 1 / 38 | |
| 2.7.0 | 1 / 38 | |
| 2.6.0 | 1 / 38 | |
| 2.5.0 | 1 / 38 | |
| 2.4.0 | 1 / 38 | |
| 2.1.0 | 1 / 39 |
v2.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.1
6 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
v2.14.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-13. This could indicate a legitimate maintainer transition or an account compromise.
v2.13.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
v2.12.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.