@commitlint/format
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@commitlint/types | AI (dependencies): @commitlint/types is a sibling package in the same commitlint monorepo; its inclusion is expected and stable across all versions of @commitlint/format. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 2 / 1 | |
| 21.0.0 | 2 / 1 | |
| 20.5.0 | 2 / 1 | |
| 20.4.4 | 2 / 1 | |
| 20.4.3 | 2 / 1 | |
| 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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.