@clerk/localizations
Localizations for the Clerk components
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dominic-clerk is a Clerk org member (47 approved pkgs, clerk-suffixed username). Rotation within org, backed by SLSA provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): dominic-clerk is a known Clerk org publisher; legitimate team rotation. | ai | |
| dependencies | unvetted-dep:@clerk/shared | AI (dependencies): @clerk/shared is a first-party Clerk internal package from the same monorepo; flagging it as unvetted is a stable false positive for all @clerk/* packages. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 4.13.3 | 1 / 0 | |
| 4.13.2 | 1 / 0 | |
| 4.13.1 | 1 / 0 | |
| 4.13.0 | 1 / 0 | |
| 4.12.1 | 1 / 0 | |
| 4.12.0 | 1 / 0 | |
| 4.11.1 | 1 / 0 | |
| 4.11.0 | 1 / 0 | |
| 4.10.0 | 1 / 0 | |
| 4.9.3 | 1 / 0 | |
| 4.9.2 | 1 / 0 | |
| 4.9.1 | 1 / 0 | |
| 4.9.0 | 1 / 0 | |
| 4.8.2 | 1 / 0 | |
| 4.8.1 | 1 / 0 | |
| 4.8.0 | 1 / 0 | |
| 4.7.2 | 1 / 0 | |
| 4.7.1 | 1 / 0 | |
| 4.7.0 | 1 / 0 | |
| 4.6.8 | 1 / 0 | |
| 4.6.7 | 1 / 0 | |
| 4.6.6 | 1 / 0 | |
| 4.6.5 | 1 / 0 | |
| 4.6.4 | 1 / 0 | |
| 4.6.3 | 1 / 0 | |
| 4.6.2 | 1 / 0 | |
| 4.6.1 | 1 / 0 | |
| 4.6.0 | 1 / 0 | |
| 4.5.8 | 1 / 0 | |
| 4.5.7 | 1 / 0 | |
| 4.5.6 | 1 / 0 | |
| 4.5.5 | 1 / 0 | |
| 4.5.4 | 1 / 0 | |
| 4.5.3 | 1 / 0 | |
| 4.5.2 | 1 / 0 | |
| 4.5.1 | 1 / 0 | |
| 4.5.0 | 1 / 0 | |
| 4.4.1 | 1 / 0 | |
| 4.4.0 | 1 / 0 | |
| 4.3.2 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.4 | 1 / 0 | |
| 4.2.3 | 1 / 0 | |
| 4.2.2 | 1 / 0 | |
| 4.2.1 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.37.8 | 1 / 0 | |
| 3.37.7 | 1 / 0 | |
| 3.37.6 | 1 / 0 | |
| 3.37.5 | 1 / 0 |
v4.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.37.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.37.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.37.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.