← Back to Scanner

paperclip Security Audit Report

πŸ”­ Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

paperclip is an AI agent skill, created by paperclipai and published at paperclipai/paperclip. ClawSecure audited paperclip across 66 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 3 findings concentrate in Code Injection, Permissions Manifest and ReDoS, including Potentially dangerous code pattern detected: eval\( and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is paperclip safe?

ClawSecure audited paperclip and assigned a security score of 80/100 (Safe), identifying 3 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in paperclip?

ClawSecure identified 3 findings in paperclip, concentrated in Code Injection, Permissions Manifest and ReDoS. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: eval\( and Missing config.json - agent may not be properly configured.

How was paperclip audited?

ClawSecure ran paperclip through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 66 files from paperclipai/paperclip.

What does a score of 80 mean?

ClawSecure assigned paperclip a security score of 80/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for paperclip

ClawSecure detected 3 security findings in paperclip, spanning Code Injection, Permissions Manifest and ReDoS.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for paperclip

Eliminate dynamic code execution
paperclip evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Fix ReDoS-prone patterns
paperclip contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

browserScore 95/100summarizeScore 85/100browserScore 95/100pdfScore 93/100summarizeScore 85/100

Scanned on August 12, 2026. paperclip is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan