@strapi/types
Shared typescript types for Strapi internal use
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): alexandrebodin is a long-standing Strapi core maintainer (3230 days, 12955 approved). Rotation within the Strapi team is expected. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Artifact of v4→v5 major version gap in approval pipeline; v5.x has been actively published. Not true dormancy. | ai | |
| dependencies | unvetted-dep:typedoc-github-wiki-theme | AI (dependencies): typedoc-github-wiki-theme is a standard TypeDoc theme for documentation; phantom-dep finding confirms it is not directly imported at runtime. | ai | |
| dependencies | unvetted-dep:@koa/cors | AI (dependencies): @koa/cors is a well-known Koa CORS middleware; legitimate dependency for a Strapi types package referencing Koa internals. | ai | |
| dependencies | unvetted-dep:@casl/ability | AI (dependencies): @casl/ability is a widely-used, reputable authorization library; stable dependency for Strapi's permission types. | ai | |
| dependencies | unvetted-dep:typedoc-plugin-markdown | AI (dependencies): typedoc-plugin-markdown is a standard TypeDoc plugin for documentation generation; phantom-dep finding confirms it is not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:typedoc | AI (phantom-deps): typedoc is a documentation tool referenced in config files; misplaced in dependencies vs devDependencies but poses no security risk. | 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 packages historically do not publish with Sigstore provenance; this is consistent across the entire monorepo and not a security signal. | ai | |
| phantom-deps | phantom-dep:typedoc-plugin-markdown | AI (phantom-deps): Documentation tooling referenced in config only; no security risk. | ai | |
| phantom-deps | phantom-dep:typedoc-github-wiki-theme | AI (phantom-deps): Documentation tooling referenced in config only; no security risk. | ai | |
| phantom-deps | phantom-dep:@koa/cors | AI (phantom-deps): @koa/cors is a legitimate Koa middleware; referenced in type definitions for a types-only package, no security risk. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 17 / 11 | |
| 5.47.0 | 17 / 11 | |
| 5.46.1 | 16 / 11 | |
| 5.46.0 | 16 / 11 | |
| 5.45.1 | 16 / 11 | |
| 5.45.0 | 16 / 11 | |
| 5.44.0 | 16 / 11 | |
| 5.43.0 | 16 / 11 | |
| 5.42.1 | 16 / 11 | |
| 5.42.0 | 16 / 11 | |
| 5.41.1 | 16 / 11 | |
| 5.41.0 | 16 / 11 | |
| 5.40.0 | 16 / 11 | |
| 5.39.0 | 16 / 11 | |
| 5.38.1 | 16 / 11 | |
| 5.38.0 | 16 / 11 | |
| 5.37.1 | 16 / 11 | |
| 5.37.0 | 16 / 11 | |
| 5.36.1 | 16 / 11 | |
| 5.36.0 | 16 / 11 | |
| 5.35.0 | 16 / 11 | |
| 5.34.0 | 16 / 11 | |
| 5.33.4 | 16 / 11 | |
| 5.33.3 | 16 / 11 | |
| 5.33.2 | 16 / 11 | |
| 5.33.1 | 16 / 11 | |
| 5.33.0 | 16 / 11 | |
| 5.32.0 | 16 / 11 | |
| 5.31.3 | 16 / 11 | |
| 5.31.2 | 16 / 11 | |
| 5.31.1 | 16 / 11 | |
| 5.31.0 | 16 / 11 | |
| 5.30.1 | 16 / 11 | |
| 5.30.0 | 16 / 11 | |
| 5.29.0 | 16 / 11 | |
| 5.28.0 | 16 / 11 | |
| 5.27.0 | 16 / 11 | |
| 5.26.0 | 16 / 11 | |
| 5.25.0 | 16 / 11 | |
| 5.24.2 | 16 / 11 | |
| 5.24.1 | 16 / 11 | |
| 5.24.0 | 16 / 11 | |
| 5.23.6 | 16 / 11 | |
| 5.23.5 | 16 / 11 | |
| 5.23.4 | 16 / 11 | |
| 5.23.3 | 16 / 11 | |
| 5.23.2 | 16 / 11 | |
| 5.23.1 | 16 / 11 | |
| 5.23.0 | 16 / 11 | |
| 5.22.0 | 16 / 11 | |
| 5.21.0 | 16 / 11 |
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 finding[Accepted risk] Package 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.
[Accepted risk] 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.
[Accepted risk] 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.
[Accepted risk] 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.
[Accepted risk] 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.
[Accepted risk] 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.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.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.