@commitlint/parse
Lint your commit messages
82%
Total Score
100
100
89
67
Health Score Breakdown
The repository name does not match @commitlint/parse and its README does not mention the package, so the package-to-repository relationship is less transparent; the organization-owned monorepo context partly offsets this concern.
The project uses TypeScript, Vitest, and build tooling, supporting a structured development process. No security-scanning tools were detected, which leaves a modest security-process gap.
No repository security policy was found, reducing transparency for reporting vulnerabilities, although active maintenance and organization backing partly compensate.
All five workflows were analyzed with no untrusted checkout or script-injection findings, and two workflows use read-only permissions. However, 20 of 25 action references are unpinned, one workflow has top-level write permissions, and a high-confidence low-severity audit found an ad hoc package installation.
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 | — | — |
conventional-commits-parser Version ^7.0.0 | — | — |
conventional-changelog-angular Version ^9.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 23 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.