@strapi/utils
Shared utilities for the Strapi packages
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): alexandrebodin is a long-standing Strapi core maintainer (3230 days, 12955 approved versions). Publisher rotation within the Strapi team is expected. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of comparing v4→v5 major version lines; Strapi 5.x has been actively published. | ai | |
| dependencies | unvetted-dep:node-machine-id | AI (dependencies): node-machine-id is a well-known, stable package legitimately used by Strapi for machine identification (e.g., telemetry). Stable dependency across many Strapi versions. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Strapi uses a custom license file; this SPDX expression is consistent with their known licensing model across all versions. | ai |
Versions (showing 100 of 104)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 10 / 11 | |
| 5.50.2 | 10 / 11 | |
| 5.50.1 | 10 / 9 | |
| 5.50.0 | 10 / 9 | |
| 5.49.0 | 10 / 7 | |
| 5.48.1 | 10 / 7 | |
| 5.48.0 | 10 / 7 | |
| 5.47.1 | 10 / 7 | |
| 5.47.0 | 10 / 7 | |
| 5.46.1 | 10 / 7 | |
| 5.46.0 | 10 / 7 | |
| 5.45.1 | 10 / 7 | |
| 5.45.0 | 10 / 7 | |
| 5.44.0 | 10 / 7 | |
| 5.43.0 | 10 / 7 | |
| 5.42.1 | 10 / 7 | |
| 5.42.0 | 10 / 7 | |
| 5.41.1 | 10 / 7 | |
| 5.41.0 | 10 / 7 | |
| 5.35.0 | 10 / 7 | |
| 5.34.0 | 10 / 7 | |
| 5.33.4 | 10 / 7 | |
| 5.33.3 | 10 / 7 | |
| 5.33.2 | 10 / 7 | |
| 5.33.1 | 10 / 7 | |
| 5.33.0 | 10 / 7 | |
| 5.32.0 | 10 / 7 | |
| 5.31.3 | 10 / 7 | |
| 5.31.2 | 10 / 7 | |
| 5.31.1 | 10 / 7 | |
| 5.31.0 | 10 / 7 | |
| 5.30.1 | 10 / 7 | |
| 5.30.0 | 10 / 7 | |
| 5.29.0 | 10 / 7 | |
| 5.28.0 | 10 / 7 | |
| 5.27.0 | 10 / 7 | |
| 5.26.0 | 10 / 7 | |
| 5.25.0 | 10 / 7 | |
| 5.24.2 | 10 / 7 | |
| 5.24.1 | 10 / 7 | |
| 5.24.0 | 10 / 7 | |
| 5.23.6 | 10 / 7 | |
| 5.23.5 | 10 / 7 | |
| 5.23.4 | 10 / 7 | |
| 5.23.3 | 10 / 7 | |
| 5.23.2 | 10 / 7 | |
| 5.23.1 | 10 / 7 | |
| 5.23.0 | 10 / 7 | |
| 5.22.0 | 10 / 7 | |
| 5.21.0 | 10 / 7 | |
| 5.20.0 | 10 / 7 | |
| 5.19.0 | 10 / 7 | |
| 5.18.1 | 10 / 7 | |
| 5.18.0 | 10 / 7 | |
| 5.17.0 | 10 / 7 | |
| 5.16.1 | 11 / 8 | |
| 5.16.0 | 11 / 8 | |
| 5.15.1 | 11 / 8 | |
| 5.15.0 | 11 / 8 | |
| 5.14.0 | 11 / 8 | |
| 5.13.1 | 11 / 8 | |
| 5.13.0 | 10 / 7 | |
| 5.12.7 | 10 / 7 | |
| 5.12.6 | 10 / 7 | |
| 5.12.5 | 10 / 7 | |
| 5.12.4 | 10 / 7 | |
| 5.12.3 | 10 / 7 | |
| 5.12.2 | 10 / 7 | |
| 5.12.1 | 10 / 7 | |
| 5.12.0 | 10 / 7 | |
| 5.11.3 | 10 / 7 | |
| 5.11.2 | 10 / 7 | |
| 5.11.1 | 10 / 7 | |
| 5.11.0 | 10 / 7 | |
| 5.10.4 | 10 / 7 | |
| 5.10.3 | 10 / 7 | |
| 5.10.2 | 10 / 7 | |
| 5.10.1 | 10 / 7 | |
| 5.10.0 | 10 / 7 | |
| 5.9.0 | 10 / 8 | |
| 5.8.1 | 10 / 8 | |
| 5.8.0 | 10 / 8 | |
| 5.7.0 | 10 / 8 | |
| 5.6.0 | 10 / 8 | |
| 5.5.2 | 10 / 8 | |
| 5.5.1 | 10 / 8 | |
| 5.5.0 | 10 / 8 | |
| 5.4.2 | 10 / 8 | |
| 5.4.1 | 10 / 8 | |
| 5.4.0 | 10 / 8 | |
| 5.3.0 | 10 / 8 | |
| 5.2.0 | 10 / 8 | |
| 5.1.1 | 10 / 8 | |
| 5.1.0 | 10 / 8 | |
| 5.0.6 | 10 / 8 | |
| 5.0.5 | 10 / 8 | |
| 5.0.4 | 10 / 8 | |
| 5.0.3 | 10 / 8 | |
| 5.0.2 | 10 / 8 | |
| 5.0.1 | 10 / 8 |
v5.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.50.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.