@axa-fr/react-oidc
OpenID Connect & OAuth authentication using 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is a benign echo warning message; no code execution or network access. | ai | |
| phantom-deps | phantom-dep:@axa-fr/oidc-client-service-worker | AI (phantom-deps): Same-org dependency used via build scripts (copy-service-worker), not direct import; stable pattern for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.27.4 | 2 / 18 | |
| 7.27.2 | 2 / 18 | |
| 7.27.0 | 2 / 18 | |
| 7.26.6 | 2 / 18 | |
| 7.26.5 | 2 / 18 | |
| 7.26.4 | 2 / 18 | |
| 7.26.3 | 2 / 18 | |
| 7.25.15 | 2 / 18 | |
| 7.25.14 | 2 / 18 | |
| 7.25.13 | 2 / 18 | |
| 7.25.12 | 2 / 18 | |
| 7.25.11 | 2 / 18 |
v7.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.