brin
brin

conventional-changelog

npm

Is conventional-changelog safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for conventional-changelog v7.1.1. Trust score: 85/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)

conventional-changelog 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.

conventional-changelog Capabilities & Permissions

What conventional-changelog can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

/usr/ (r)/usr/ (r)package.json (r)/usr/ (r)/usr/ (r)package.json (r)package.json (r)

AGENTS.md for conventional-changelog

Good instructions lead to good results. brin adds conventional-changelog 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 →

conventional-changelog Documentation & Source Code

For the full conventional-changelog README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about conventional-changelog safety

Weekly Downloads

1.8M

Version

7.1.1

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is conventional-changelog Safe? | npm Safety Scan - brin