← Back to Scanner

api-gateway Security Audit Report

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

api-gateway is an AI agent skill, created by maton-ai and published at maton-ai/api-gateway-skill. ClawSecure audited api-gateway across 57 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 91/100 (Safe). The 4 findings concentrate in Obfuscation, Permissions Manifest and Policy Violation, including Missing config.json - agent may not be properly configured and Hidden file found: .agents/plugins/marketplace.json. Hidden…. None were rated high or critical severity.

Is api-gateway safe?

ClawSecure audited api-gateway and assigned a security score of 91/100 (Safe), identifying 4 findings across Obfuscation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in api-gateway?

ClawSecure identified 4 findings in api-gateway, concentrated in Obfuscation, Permissions Manifest and Policy Violation. The most severe include Missing config.json - agent may not be properly configured and Hidden file found: .agents/plugins/marketplace.json. Hidden….

How was api-gateway audited?

ClawSecure ran api-gateway through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 57 files from maton-ai/api-gateway-skill.

What does a score of 91 mean?

ClawSecure assigned api-gateway a security score of 91/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 4 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 api-gateway

ClawSecure detected 4 security findings in api-gateway, spanning Obfuscation, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for api-gateway

Review obfuscated or hidden code
api-gateway 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
api-gateway 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

opencode-auto-continueScore 90/100@fazaboa/opencode-auto-continueScore 95/100shodan-skillScore 90/100oh-my-claudecodeScore 80/100clawdhubScore 85/100

Scanned on August 21, 2026. api-gateway 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