@commitlint/cli
Lint your commit messages
87%
Total Score
100
100
94
75
50
Health Score Breakdown
No build attestation or trusted-publisher provenance was provided, leaving publication origin less transparent; this is a supply-chain transparency gap rather than evidence of maliciousness.
The repository uses TypeScript, Vitest, build tooling, and npm scripts, but no security scanning tools were detected; the missing scanning is a modest hygiene gap.
The repository has no security policy, reducing vulnerability-reporting transparency, though active maintenance and repository tooling provide some compensation.
All five workflows were analyzed with no untrusted checkouts or script injection, but 20 of 25 action references are unpinned and CI installs a package outside a lockfile; the single low-severity finding warrants hygiene caution.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 yargs Version ^18.0.0 | — | — |
tinyexec Version ^1.0.0 | — | — |
@commitlint/lint Version ^21.2.3 | — | — |
@commitlint/load Version ^21.2.3 | — | — |
@commitlint/read Version ^21.2.3 | — | — |
Weekly Downloads
Info
- Last Published
- 23 days ago
- Created
- 9 years ago
- Unpacked Size
- 0.1 MB
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.