@strapi/i18n
Create read and update content in different languages, both from the Admin Panel and from the API
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): react-redux is declared in dependencies and referenced in config; stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): bassel17 is a known Strapi team member (10 approved pkgs). Publisher rotation within the @strapi org is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal is normal team churn for a company-maintained package like @strapi/*. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (nico-strapi, strapi.adzouz) are clearly Strapi employees based on naming; normal org churn. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Strapi monorepo packages are not published on every release cycle; gaps in individual package publish history are expected and do not indicate account takeover for this well-established official plugin. | ai | |
| dependencies | unvetted-dep:@strapi/icons | AI (dependencies): First-party Strapi package, part of the same monorepo ecosystem. Expected dependency for all Strapi plugins. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license declaration referencing their LICENSE file; consistent across all @strapi/* packages. | ai | |
| provenance | no-provenance | AI (provenance): Strapi does not publish with Sigstore provenance; package identity is confirmed by repo URL, author metadata, and ecosystem consistency. | ai | |
| dependencies | unvetted-dep:@strapi/design-system | AI (dependencies): First-party Strapi design system package. Expected dependency for all Strapi admin plugins. | ai | |
| dependencies | unvetted-dep:@strapi/utils | AI (dependencies): First-party Strapi utility package from the same monorepo. Expected and stable dependency. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 10 / 14 | |
| 5.47.0 | 10 / 14 | |
| 5.46.1 | 10 / 14 | |
| 5.46.0 | 10 / 14 | |
| 5.45.1 | 10 / 14 | |
| 5.45.0 | 10 / 14 | |
| 5.44.0 | 10 / 14 | |
| 5.43.0 | 10 / 14 | |
| 5.42.1 | 10 / 14 | |
| 5.42.0 | 10 / 14 | |
| 5.41.1 | 10 / 14 | |
| 5.41.0 | 10 / 14 | |
| 5.40.0 | 10 / 14 | |
| 5.39.0 | 10 / 14 | |
| 5.38.1 | 10 / 14 | |
| 5.38.0 | 10 / 14 | |
| 5.37.1 | 10 / 14 | |
| 5.37.0 | 10 / 14 | |
| 5.36.1 | 10 / 14 | |
| 5.36.0 | 10 / 14 | |
| 5.35.0 | 10 / 14 | |
| 5.34.0 | 10 / 14 | |
| 5.33.4 | 10 / 14 | |
| 5.33.3 | 10 / 14 | |
| 5.33.2 | 10 / 14 | |
| 5.33.1 | 10 / 14 | |
| 5.33.0 | 10 / 14 | |
| 5.32.0 | 10 / 14 | |
| 5.31.3 | 10 / 14 | |
| 5.31.2 | 10 / 14 | |
| 5.31.1 | 10 / 14 | |
| 5.31.0 | 10 / 14 | |
| 5.30.1 | 10 / 14 | |
| 5.30.0 | 10 / 14 | |
| 5.29.0 | 10 / 13 | |
| 5.28.0 | 10 / 12 | |
| 5.27.0 | 10 / 12 | |
| 5.26.0 | 10 / 12 | |
| 5.25.0 | 10 / 12 | |
| 5.24.2 | 10 / 12 | |
| 5.24.1 | 10 / 12 | |
| 5.24.0 | 10 / 12 | |
| 5.23.6 | 10 / 12 | |
| 5.23.5 | 10 / 12 | |
| 5.23.4 | 10 / 12 | |
| 5.23.3 | 10 / 12 | |
| 5.23.2 | 10 / 12 | |
| 5.23.1 | 10 / 12 | |
| 5.23.0 | 10 / 12 | |
| 5.22.0 | 10 / 12 | |
| 5.21.0 | 10 / 12 | |
| 5.20.0 | 10 / 12 | |
| 5.19.0 | 9 / 12 | |
| 5.18.1 | 9 / 12 | |
| 5.18.0 | 9 / 12 | |
| 5.17.0 | 9 / 12 | |
| 5.16.1 | 9 / 12 | |
| 5.16.0 | 9 / 12 | |
| 5.15.1 | 9 / 12 | |
| 5.15.0 | 9 / 12 | |
| 5.14.0 | 9 / 12 | |
| 5.13.1 | 9 / 12 | |
| 5.13.0 | 9 / 12 | |
| 5.12.7 | 9 / 12 |
v5.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.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.
v5.42.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.
v5.41.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.
v5.41.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.
v5.40.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.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.
v5.30.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.
v5.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.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.
v5.14.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.
v5.13.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.
v5.13.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.