@strapi/typescript-utils
Typescript support for Strapi
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 |
|---|---|---|---|---|
| typosquat | typosquat.pattern:typescript | AI (typosquat): @strapi/typescript-utils is a legitimate Strapi org package providing TypeScript utilities, not a typosquat of 'typescript'. Scoped under @strapi with matching repo. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 6 / 1 | |
| 5.47.0 | 6 / 1 | |
| 5.46.1 | 6 / 1 | |
| 5.46.0 | 6 / 1 | |
| 5.45.1 | 6 / 1 | |
| 5.45.0 | 6 / 1 | |
| 5.44.0 | 6 / 1 | |
| 5.43.0 | 6 / 1 | |
| 5.42.1 | 6 / 1 | |
| 5.42.0 | 6 / 1 | |
| 5.41.1 | 6 / 1 | |
| 5.41.0 | 6 / 1 | |
| 5.31.3 | 6 / 1 | |
| 5.31.2 | 6 / 1 | |
| 5.31.1 | 6 / 1 | |
| 5.31.0 | 6 / 1 | |
| 5.30.1 | 6 / 1 | |
| 5.30.0 | 6 / 1 | |
| 5.29.0 | 6 / 1 | |
| 5.28.0 | 6 / 1 | |
| 5.27.0 | 6 / 1 | |
| 5.26.0 | 6 / 1 | |
| 5.25.0 | 6 / 1 | |
| 5.24.2 | 6 / 1 | |
| 5.24.1 | 6 / 1 | |
| 5.24.0 | 6 / 1 | |
| 5.23.6 | 6 / 1 | |
| 5.23.5 | 6 / 1 | |
| 5.23.4 | 6 / 1 | |
| 5.23.3 | 6 / 1 | |
| 5.23.2 | 6 / 1 | |
| 5.23.1 | 6 / 1 | |
| 5.23.0 | 6 / 1 | |
| 5.22.0 | 6 / 1 | |
| 5.21.0 | 6 / 1 | |
| 5.20.0 | 6 / 1 | |
| 5.19.0 | 6 / 1 | |
| 5.18.1 | 6 / 1 | |
| 5.18.0 | 6 / 1 | |
| 5.17.0 | 6 / 1 | |
| 5.16.1 | 6 / 1 | |
| 5.16.0 | 6 / 1 | |
| 5.15.1 | 6 / 1 | |
| 5.15.0 | 6 / 1 | |
| 5.14.0 | 6 / 1 | |
| 5.13.1 | 6 / 1 | |
| 5.13.0 | 6 / 1 | |
| 5.12.7 | 6 / 1 | |
| 4.26.0 | 6 / 0 |
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
2 findingsPackage name '@strapi/typescript-utils' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'typescript'.
Package 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.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.26.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.
v5.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage 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.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.