← Back to Scanner

pi-orchestration Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

pi-orchestration is an AI agent skill, created by dbhurley and published at openclaw/skills. ClawSecure audited pi-orchestration across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Policy Violation, Command Injection and Permissions Manifest, including Pattern detected: os.system( and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is pi-orchestration safe?

ClawSecure audited pi-orchestration and assigned a security score of 85/100 (Safe), identifying 3 findings across Policy Violation and Command Injection. Review the findings below before installing.

What did ClawSecure find in pi-orchestration?

ClawSecure identified 3 findings in pi-orchestration, concentrated in Policy Violation, Command Injection and Permissions Manifest. 1 was rated high or critical severity. The most severe include Pattern detected: os.system( and Missing config.json - agent may not be properly configured.

How was pi-orchestration audited?

ClawSecure ran pi-orchestration through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 3 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned pi-orchestration a security score of 85/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 pi-orchestration

ClawSecure detected 3 security findings in pi-orchestration, spanning Policy Violation, Command Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for pi-orchestration

Resolve policy violations
pi-orchestration trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Harden command execution
pi-orchestration constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
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.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolWhy Generic Scanners Fail at AI Agent Security

Related AI Agent Security Audits

hermes-agentScore 85/100Agent-ReachScore 85/100agent-skillsScore 95/100agent-creditScore 75/100Self-Improving Agent (With Self-Reflection)Score 93/100

Scanned on February 7, 2026. pi-orchestration 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