brin
brin

so-acceptance

npm

Is so-acceptance safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for so-acceptance v7.0.0-beta-v4. 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)

so-acceptance 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.

so-acceptance Capabilities & Permissions

What so-acceptance 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 (r)

AGENTS.md for so-acceptance

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

so-acceptance Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about so-acceptance safety

Weekly Downloads

35

Version

7.0.0-beta-v4

License

GPL-2.0

Last Scanned

2 hours ago

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Is so-acceptance Safe? | npm Safety Scan - brin