@changesets/git

npm

Is @changesets/git safe to use?

The latest brin safety scan flagged @changesets/git v3.0.4 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)

@changesets/git Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • Can spawn child processes

brin Recommendations

  • This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add @changesets/git 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.

@changesets/git Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

git

AGENTS.md for @changesets/git

Good instructions lead to good results. brin adds @changesets/git 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 →

@changesets/git Documentation & Source Code

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

Frequently asked questions about @changesets/git safety

Weekly Downloads

1.9M

Version

3.0.4

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is @changesets/git Safe? | npm Safety Scan - brin