@strapi/database
Strapi's database layer
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (nico-strapi, strapi.adzouz) carry Strapi branding; consistent with internal team rotation at Strapi Solutions SAS. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainer (remidej) is consistent with Strapi team rotation, not a hostile takeover. Publisher is a verified Strapi team member. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a legitimate, widely-used package; phantom dep finding reflects indirect/config usage, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv is a legitimate, well-known JSON schema validation library; phantom dep finding reflects indirect/config usage, not a risk for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Gap explained by major version transition (v4→v5). Strapi is an active project; dormancy in this sub-package reflects the v5 development cycle. | ai | |
| provenance | publisher-changed | AI (provenance): alexandrebodin is a long-standing Strapi core maintainer (3230 days, 12955 approved). Publisher rotation within the Strapi team is expected. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi licensing pattern across all @strapi/* packages; references a LICENSE file in the repo. | ai | |
| dependencies | unvetted-dep:knex | AI (dependencies): knex is a well-established SQL query builder with millions of weekly downloads; its use in @strapi/database is expected and legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a core internal package in the Strapi monorepo; sparse README and no keywords are expected for internal packages, not spam indicators. | ai | |
| dependencies | unvetted-dep:@strapi/utils | AI (dependencies): @strapi/utils is Strapi's own utility package, a natural dependency for other Strapi core packages. | ai | |
| dependencies | unvetted-dep:umzug | AI (dependencies): umzug is a standard migration framework; its use in Strapi's database layer is expected and documented. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 10 / 3 | |
| 5.47.0 | 10 / 3 | |
| 5.46.1 | 10 / 3 | |
| 5.46.0 | 10 / 3 | |
| 5.45.1 | 10 / 3 | |
| 5.45.0 | 10 / 3 | |
| 5.44.0 | 10 / 3 | |
| 5.43.0 | 10 / 3 | |
| 5.42.1 | 10 / 3 | |
| 5.42.0 | 10 / 3 | |
| 5.41.1 | 10 / 3 | |
| 5.41.0 | 10 / 3 | |
| 5.40.0 | 10 / 3 | |
| 5.39.0 | 10 / 3 | |
| 5.38.1 | 10 / 3 | |
| 5.38.0 | 10 / 3 | |
| 5.37.1 | 10 / 3 | |
| 5.37.0 | 10 / 3 | |
| 5.36.1 | 10 / 3 | |
| 5.36.0 | 10 / 3 | |
| 5.35.0 | 10 / 3 | |
| 5.34.0 | 10 / 3 | |
| 5.33.4 | 10 / 3 | |
| 5.33.3 | 10 / 3 | |
| 5.33.2 | 10 / 3 | |
| 5.33.1 | 10 / 3 | |
| 5.33.0 | 10 / 3 | |
| 5.32.0 | 10 / 3 | |
| 5.31.3 | 10 / 3 | |
| 5.31.2 | 10 / 3 | |
| 5.31.1 | 10 / 3 | |
| 5.31.0 | 10 / 3 | |
| 5.30.1 | 10 / 3 | |
| 5.30.0 | 10 / 3 | |
| 5.29.0 | 10 / 3 | |
| 5.28.0 | 10 / 3 | |
| 5.27.0 | 10 / 3 | |
| 5.26.0 | 10 / 3 | |
| 5.25.0 | 10 / 3 | |
| 5.24.2 | 10 / 3 | |
| 5.24.1 | 10 / 3 | |
| 5.24.0 | 10 / 3 | |
| 5.23.6 | 10 / 3 | |
| 5.23.5 | 10 / 3 | |
| 5.23.4 | 10 / 3 | |
| 5.23.3 | 10 / 3 | |
| 5.23.2 | 10 / 3 | |
| 5.23.1 | 10 / 3 | |
| 5.23.0 | 10 / 3 | |
| 5.22.0 | 10 / 3 | |
| 5.21.0 | 10 / 3 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.3
2 findingsThis version was published by a different npm account than previous versions on 2025-12-03. 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.2
2 findingsThis version was published by a different npm account than previous versions on 2025-11-20. 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.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-19. 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.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-12. 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.30.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. 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.30.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-30. 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.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.