← Back to Scanner

polymarket-analysis Security Audit Report

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

polymarket-analysis is an AI agent skill, created by lukebaze and published at openclaw/skills. ClawSecure audited polymarket-analysis across 11 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 3 findings concentrate in Unauthorized Tool Use, Permissions Manifest and Policy Violation, including Undeclared Network Access and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is polymarket-analysis safe?

ClawSecure audited polymarket-analysis and assigned a security score of 90/100 (Safe), identifying 3 findings across Unauthorized Tool Use and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in polymarket-analysis?

ClawSecure identified 3 findings in polymarket-analysis, concentrated in Unauthorized Tool Use, Permissions Manifest and Policy Violation. The most severe include Undeclared Network Access and Missing config.json - agent may not be properly configured.

How was polymarket-analysis audited?

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

What does a score of 90 mean?

ClawSecure assigned polymarket-analysis a security score of 90/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 3 findings detected are lower-severity. 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 polymarket-analysis

ClawSecure detected 3 security findings in polymarket-analysis, spanning Unauthorized Tool Use, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for polymarket-analysis

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.
Resolve policy violations
polymarket-analysis trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

How to Secure an MCP Server: The 2026 Guide→What Is MCP Security? Model Context Protocol Explained→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

clippyScore 90/100stock-market-apiScore 95/100gtsec-smart-stock-selection (1)Score 95/100gtsec-smart-stock-selectionScore 95/100gtsec-smart-stock-selectionScore 95/100

Scanned on May 1, 2026. polymarket-analysis 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