@commitlint/parse
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:parcel | AI (typosquat): @commitlint/parse is a long-established scoped package in the commitlint monorepo; the Levenshtein match to 'parcel' is a false positive with no plausible typosquat relationship. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 21.0.2 | 3 / 2 | |
| 21.0.1 | 3 / 2 | |
| 21.0.0 | 3 / 3 | |
| 20.5.0 | 3 / 3 | |
| 20.4.4 | 3 / 3 | |
| 20.4.3 | 3 / 3 | |
| 20.4.1 | 3 / 2 | |
| 20.4.0 | 3 / 2 | |
| 20.3.1 | 3 / 3 | |
| 20.2.0 | 3 / 3 | |
| 20.0.0 | 3 / 3 |
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.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.