@commitlint/cli

npm

Is @commitlint/cli safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @commitlint/cli v20.4.2. Trust score: 75/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

@commitlint/cli Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

@commitlint/cli Capabilities & Permissions

What @commitlint/cli can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

GIT_PARAMSHUSKY_GIT_PARAMS

AGENTS.md for @commitlint/cli

Good instructions lead to good results. brin adds @commitlint/cli documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

@commitlint/cli Documentation & Source Code

For the full @commitlint/cli README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @commitlint/cli safety

Weekly Downloads

5.3M

Version

20.4.2

License

MIT

Other Versions

Last Scanned

1 day ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: GIT_PARAMS, HUSKY_GIT_PARAMS

Is @commitlint/cli Safe? | npm Safety Scan - brin