Caveat verdict

beeper-api-cli

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Messaging CLI requiring explicit user approval before sending any message and connecting only to localhost Beeper API.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

35
security
60
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (2)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="paste-your-token-here

Pattern match high

HTTP request to bare IP address — common in malicious payloads

SKILL.md · code · http://192.168.1.100

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API