@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, 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 |
|---|---|---|---|---|
| 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 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 6 / 7 | |
| 5.50.2 | 6 / 7 | |
| 5.50.1 | 6 / 1 | |
| 5.50.0 | 6 / 1 | |
| 5.49.0 | 6 / 1 | |
| 5.48.1 | 6 / 1 | |
| 5.48.0 | 6 / 1 | |
| 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 | |
| 5.12.6 | 6 / 1 | |
| 5.12.5 | 6 / 1 | |
| 5.12.4 | 6 / 1 | |
| 5.12.3 | 6 / 1 | |
| 5.12.2 | 6 / 1 | |
| 5.12.1 | 6 / 1 | |
| 5.12.0 | 6 / 1 | |
| 5.11.3 | 6 / 1 | |
| 5.11.2 | 6 / 1 | |
| 5.11.1 | 6 / 1 | |
| 5.11.0 | 6 / 1 | |
| 5.10.4 | 6 / 1 | |
| 5.10.3 | 6 / 1 | |
| 5.10.2 | 6 / 1 | |
| 5.10.1 | 6 / 1 | |
| 5.10.0 | 6 / 1 | |
| 5.9.0 | 6 / 1 | |
| 5.8.1 | 6 / 1 | |
| 5.8.0 | 6 / 1 | |
| 5.7.0 | 6 / 1 | |
| 5.6.0 | 6 / 1 | |
| 5.5.2 | 6 / 1 | |
| 5.5.1 | 6 / 1 | |
| 5.5.0 | 6 / 1 | |
| 5.4.2 | 6 / 1 | |
| 5.4.1 | 6 / 1 | |
| 5.4.0 | 6 / 1 | |
| 5.3.0 | 6 / 1 | |
| 5.2.0 | 6 / 1 | |
| 5.1.1 | 6 / 1 | |
| 5.1.0 | 6 / 1 | |
| 5.0.6 | 6 / 1 | |
| 5.0.5 | 6 / 1 | |
| 5.0.4 | 6 / 1 | |
| 5.0.3 | 6 / 1 | |
| 5.0.2 | 6 / 1 | |
| 5.0.1 | 6 / 1 | |
| 5.0.0 | 6 / 1 | |
| 4.26.2 | 6 / 0 | |
| 4.26.0 | 6 / 0 |
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.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.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.