reaper

npm

Is reaper safe to use?

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

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

reaper Capabilities & Permissions

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

Environment Variables

Accesses the following environment variables.

REAPER_COVERAGE

AGENTS.md for reaper

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

reaper Documentation & Source Code

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

Frequently asked questions about reaper safety

Weekly Downloads

55

Version

0.3.2

License

MIT

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: REAPER_COVERAGE

Is reaper Safe? | npm Safety Scan - brin