somebody

npm

Is somebody safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for somebody v3.0.0. Trust score: 65/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)

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

somebody Capabilities & Permissions

What somebody 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.

AGENTS.md for somebody

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

somebody Documentation & Source Code

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

Frequently asked questions about somebody safety

Weekly Downloads

212

Version

3.0.0

License

MIT

Last Scanned

5 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is somebody Safe? | npm Safety Scan - brin