@strapi/upgrade
CLI to upgrade Strapi applications effortless
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Strapi monorepo package; dormancy reflects independent release cadence of the upgrade tool, not account takeover. No material code changes observed. | ai | |
| provenance | publisher-changed | AI (provenance): bassel17 is a Strapi team member with 9 approved packages and 0 rejected; publisher rotation within the Strapi org is expected and not a security concern. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): ora is a legitimate declared dependency used in build/test config; phantom detection is a false positive for this package's tooling setup. | ai | |
| phantom-deps | phantom-dep:memfs | AI (phantom-deps): memfs is a legitimate declared dependency used in test config (in-memory filesystem); phantom detection is a false positive for this package. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license declaration pattern across all @strapi/* packages; not a security concern. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 16 / 5 | |
| 5.47.0 | 16 / 5 | |
| 5.46.1 | 16 / 5 | |
| 5.46.0 | 16 / 5 | |
| 5.45.1 | 16 / 5 | |
| 5.45.0 | 16 / 5 | |
| 5.44.0 | 16 / 5 | |
| 5.43.0 | 16 / 5 | |
| 5.42.1 | 16 / 5 | |
| 5.42.0 | 16 / 5 | |
| 5.41.1 | 16 / 5 | |
| 5.41.0 | 16 / 5 | |
| 5.40.0 | 16 / 5 | |
| 5.39.0 | 16 / 5 | |
| 5.38.1 | 16 / 5 | |
| 5.38.0 | 16 / 5 | |
| 5.37.1 | 16 / 5 | |
| 5.37.0 | 16 / 5 | |
| 5.36.1 | 16 / 5 | |
| 5.36.0 | 16 / 5 | |
| 5.35.0 | 16 / 5 | |
| 5.34.0 | 16 / 5 | |
| 5.33.4 | 16 / 5 | |
| 5.33.3 | 16 / 5 | |
| 5.33.2 | 16 / 5 | |
| 5.33.1 | 16 / 5 | |
| 5.33.0 | 16 / 5 | |
| 5.32.0 | 16 / 5 | |
| 5.31.3 | 16 / 5 | |
| 5.31.2 | 16 / 5 | |
| 5.31.1 | 16 / 5 | |
| 5.31.0 | 15 / 5 | |
| 5.30.1 | 15 / 5 | |
| 5.30.0 | 15 / 5 | |
| 5.29.0 | 15 / 5 | |
| 5.28.0 | 15 / 5 | |
| 5.27.0 | 15 / 5 | |
| 5.26.0 | 15 / 5 | |
| 5.25.0 | 15 / 5 | |
| 5.24.2 | 15 / 5 | |
| 5.24.1 | 15 / 5 | |
| 5.24.0 | 15 / 5 | |
| 5.23.6 | 15 / 5 | |
| 5.23.5 | 15 / 5 | |
| 5.23.4 | 15 / 5 | |
| 5.23.3 | 15 / 5 | |
| 5.23.2 | 15 / 5 | |
| 5.23.1 | 15 / 5 | |
| 5.23.0 | 15 / 5 | |
| 5.22.0 | 15 / 5 | |
| 5.21.0 | 15 / 5 |
v5.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.0
1 findingPackage 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.