enpeem

npm

Is enpeem safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for enpeem v2.2.0. Trust score: 75/100. 1 known CVE, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

enpeem Passed Security Checks

No security concerns detected

clean
CVEs

1

Threats

0

Install Scripts

0

Risk Indicators

  • GHSA-hmw2-mvvh-jf5j: UNKNOWN

enpeem CVE Vulnerabilities (1)

OS Command Injection in enpeem

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.

enpeem Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

node_modules (r)package.json (r)

Process Spawning

This package can spawn child processes.

npm

AGENTS.md for enpeem

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

enpeem Documentation & Source Code

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

Frequently asked questions about enpeem safety

Weekly Downloads

159

Version

2.2.0

License

MIT

Last Scanned

1 day ago

Trust Score

75/100·Legitimacy signals, not safety

CVEs (1)

GHSA-hmw2-mvvh-jf5j

OS Command Injection in enpeem

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is enpeem Safe? | npm Safety Scan - brin