← Back to Scanner

omnisearch Security Audit Report

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

omnisearch is an AI agent skill, created by bguidolim and published at openclaw/skills. ClawSecure audited omnisearch across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 95/100 (Safe). The 2 findings concentrate in Policy Violation and Permissions Manifest, including Missing config.json - agent may not be properly configured and Skill manifest does not include a 'license' field. Specifying a license.... None were rated high or critical severity.

Is omnisearch safe?

ClawSecure audited omnisearch and assigned a security score of 95/100 (Safe), identifying 2 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in omnisearch?

ClawSecure identified 2 findings in omnisearch, concentrated in Policy Violation and Permissions Manifest. The most severe include Missing config.json - agent may not be properly configured and Skill manifest does not include a 'license' field. Specifying a license....

How was omnisearch audited?

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

What does a score of 95 mean?

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

ClawSecure detected 2 security findings in omnisearch, spanning Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for omnisearch

Resolve policy violations
omnisearch trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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 ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

summarizeScore 85/100summarizeScore 85/100academic-glowup (1)Score 95/100pdfScore 95/100kingdom-mid-search-1.4Score 95/100

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