precinct

npm

Is precinct safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for precinct v12.2.0. 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)

precinct 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.

precinct Capabilities & Permissions

What precinct 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)package.json (r)

AGENTS.md for precinct

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

precinct Documentation & Source Code

For the full precinct README, API documentation, and source code, visit the official package registry.

Frequently asked questions about precinct safety

Weekly Downloads

3.0M

Version

12.2.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is precinct Safe? | npm Safety Scan - brin