brin
brin

@changesets/read

npm

Is @changesets/read safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @changesets/read v0.6.6. 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)

@changesets/read 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.

@changesets/read Capabilities & Permissions

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

Filesystem Access

Reads and writes to the filesystem.

package.json (rw)

AGENTS.md for @changesets/read

Good instructions lead to good results. brin adds @changesets/read 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/read Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about @changesets/read safety

Weekly Downloads

1.9M

Version

0.6.6

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

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