← Back to Scanner

places Security Audit Report

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

places is an AI agent skill, created by barneyjm and published at openclaw/skills. ClawSecure audited places across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 3 findings concentrate in Policy Violation, Command Injection and Permissions Manifest, including Detects command injection patterns in agent skills: shell operators,... and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is places safe?

ClawSecure audited places and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Policy Violation and Command Injection. Review the findings below before installing.

What did ClawSecure find in places?

ClawSecure identified 3 findings in places, concentrated in Policy Violation, Command Injection and Permissions Manifest. 1 was rated high or critical severity. The most severe include Detects command injection patterns in agent skills: shell operators,... and Missing config.json - agent may not be properly configured.

How was places audited?

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

What does a score of 75 mean?

ClawSecure assigned places a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Policy Violation that warrant review before production use. 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 places

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

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for places

Resolve policy violations
places 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
places 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

skillsScore 85/100openclaw-skillsScore 85/100crewAIScore 65/100remindctlScore 69/100GitNexusScore 75/100

Scanned on February 9, 2026. places 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