← Back to Scanner

multi-search-engine Security Audit Report

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

multi-search-engine is an AI agent skill, created by gpyangyoujun and published at openclaw/skills. ClawSecure audited multi-search-engine across 7 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 93/100 (Safe). The 3 findings concentrate in ReDoS, Verification and Policy Violation, including ReDoS vulnerability: Nested quantifiers (potential… and No GitHub source URL - cannot verify agent origin. None were rated high or critical severity.

Is multi-search-engine safe?

ClawSecure audited multi-search-engine and assigned a security score of 93/100 (Safe), identifying 3 findings across ReDoS and Verification. Review the findings below before installing.

What did ClawSecure find in multi-search-engine?

ClawSecure identified 3 findings in multi-search-engine, concentrated in ReDoS, Verification and Policy Violation. The most severe include ReDoS vulnerability: Nested quantifiers (potential… and No GitHub source URL - cannot verify agent origin.

How was multi-search-engine audited?

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

What does a score of 93 mean?

ClawSecure assigned multi-search-engine a security score of 93/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 multi-search-engine

ClawSecure detected 3 security findings in multi-search-engine, spanning ReDoS, Verification and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for multi-search-engine

Fix ReDoS-prone patterns
multi-search-engine contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
Resolve policy violations
multi-search-engine 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.
Add a config.json permissions manifest
A config.json file declares what permissions an agent component needs: file system access, network requests, shell execution and more. Without it, users have no visibility into what the component can do before installing. Adding a permissions manifest is the single most impactful security improvement for any AI agent skill.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

TestFilesScore 95/100redditScore 80/100deep-research-proScore 85/100gogScore 95/100sql-toolkitScore 95/100

Scanned on March 3, 2026. multi-search-engine 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