@commitlint/rules
Lint your commit messages
91%
Total Score
100
100
94
75
50
Health Score Breakdown
No build attestation or trusted-publisher provenance is available, leaving publication origin less independently verifiable; this is a transparency gap rather than evidence of unsafe code.
The project uses TypeScript, Vitest, build tooling, and npm scripts, but no security-scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy, making vulnerability reporting and disclosure expectations less transparent.
All five workflows were analyzed without untrusted checkouts or script injection, and only one low-severity high-confidence finding was reported; however, 20 of 25 actions are unpinned and CI installs a package outside a lockfile, weakening reproducibility.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 @commitlint/types Version ^21.2.3 | — | — |
@commitlint/ensure Version ^21.2.3 | — | — |
@commitlint/message Version ^21.2.0 | — | — |
@commitlint/to-lines Version ^21.0.1 | — | — |
Weekly Downloads
Info
- Last Published
- 21 days ago
- Created
- 8 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.