← Back to Scanner

table-to-crud Security Audit Report

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

table-to-crud is an AI agent skill. ClawSecure audited table-to-crud across 4 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 Obfuscation, Permissions Manifest and Policy Violation, including File 'example_asset.txt' extension (.txt) suggests one… and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is table-to-crud safe?

ClawSecure audited table-to-crud and assigned a security score of 90/100 (Safe), identifying 3 findings across Obfuscation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in table-to-crud?

ClawSecure identified 3 findings in table-to-crud, concentrated in Obfuscation, Permissions Manifest and Policy Violation. The most severe include File 'example_asset.txt' extension (.txt) suggests one… and Missing config.json - agent may not be properly configured.

How was table-to-crud audited?

ClawSecure ran table-to-crud through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 4 files.

What does a score of 90 mean?

ClawSecure assigned table-to-crud 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 table-to-crud

ClawSecure detected 3 security findings in table-to-crud, spanning Obfuscation, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for table-to-crud

Review obfuscated or hidden code
table-to-crud contains obfuscated or hidden content that resists review. Inspect encoded, minified or hidden files to confirm they are not concealing unexpected behavior before installing.
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
table-to-crud 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

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

songseeScore 95/100goplacesScore 95/100gogcliScore 95/100ui-ux-pro-max-skillScore 75/100clawdhubScore 75/100

Scanned on June 12, 2026. table-to-crud 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