@commitlint/types
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/conventional-commits-parser | AI (phantom-deps): This is a types package that legitimately depends on @types/conventional-commits-parser as a runtime dep for type re-exports; not a phantom dependency. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 2 / 1 | |
| 21.0.0 | 2 / 2 | |
| 20.5.0 | 2 / 2 | |
| 20.4.4 | 2 / 2 | |
| 20.4.3 | 2 / 2 | |
| 20.4.0 | 2 / 1 | |
| 20.3.1 | 2 / 1 | |
| 20.2.0 | 2 / 1 | |
| 20.0.0 | 2 / 1 |
v21.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.