@commitlint/read
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.levenshtein:react | AI (typosquat): Scoped package @commitlint/read is a legitimate part of the commitlint monorepo; Levenshtein proximity to 'react' is coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:@commitlint/types | AI (phantom-deps): Sibling monorepo package used for TypeScript types; phantom-dep flag is a false positive in this monorepo context. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 21.0.2 | 4 / 3 | |
| 21.0.1 | 4 / 3 | |
| 21.0.0 | 4 / 3 | |
| 20.5.0 | 5 / 4 | |
| 20.4.4 | 5 / 4 | |
| 20.4.3 | 5 / 4 | |
| 20.4.0 | 5 / 4 | |
| 20.3.1 | 5 / 4 | |
| 20.2.0 | 5 / 4 | |
| 20.0.0 | 5 / 4 |
v21.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.