conventional-commits-parser
npmIs conventional-commits-parser safe to use?
The latest brin safety scan flagged conventional-commits-parser v6.2.1 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 75/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
conventional-commits-parser Has Warnings
Warnings detected due to potential concerns
0
0
0
Risk Indicators
- •Can spawn child processes
brin Recommendations
- →This package has warnings detected. Evaluate the specific concerns before proceeding.
Install with brin add conventional-commits-parser to automatically apply these checks before installation.
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.
conventional-commits-parser Capabilities & Permissions
What conventional-commits-parser can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads from the filesystem.
Process Spawning
This package can spawn child processes.
AGENTS.md for conventional-commits-parser
Good instructions lead to good results. brin adds conventional-commits-parser documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
conventional-commits-parser Documentation & Source Code
For the full conventional-commits-parser README, API documentation, and source code, visit the official package registry.
Frequently asked questions about conventional-commits-parser safety
Install (safety-checked)
Weekly Downloads
Version
6.2.1License
MITLast Scanned
Trust Score
Capabilities
Reads files
Spawns child processes