@datocms/cma-schema-types-generator
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): New publisher stefanoverna is the listed package author with strong track record; legitimate maintainer transition within DatoCMS org. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier is a declared runtime dependency used via @prettier/sync; phantom-dep heuristic misfires here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.4.21 | 3 / 1 | |
| 5.4.20 | 3 / 1 | |
| 5.4.18 | 3 / 1 | |
| 5.4.17 | 3 / 1 | |
| 5.4.16 | 3 / 1 | |
| 5.4.15 | 3 / 1 | |
| 5.4.14 | 3 / 1 | |
| 5.4.13 | 3 / 1 | |
| 5.4.12 | 3 / 1 |
v5.4.21
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.4.20
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.4.18
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. 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.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.