← Back to Scanner

bring-add Security Audit Report

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

bring-add is an AI agent skill, created by darkdevelopers and published at openclaw/skills. ClawSecure audited bring-add across 6 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 Policy Violation, Permissions Manifest and Supply Chain, including Missing config.json - agent may not be properly configured and Unpinned dependency: bring-shopping (version: *) - pin to specific.... None were rated high or critical severity.

Is bring-add safe?

ClawSecure audited bring-add and assigned a security score of 90/100 (Safe), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in bring-add?

ClawSecure identified 3 findings in bring-add, concentrated in Policy Violation, Permissions Manifest and Supply Chain. The most severe include Missing config.json - agent may not be properly configured and Unpinned dependency: bring-shopping (version: *) - pin to specific....

How was bring-add audited?

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

What does a score of 90 mean?

ClawSecure assigned bring-add 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 bring-add

ClawSecure detected 3 security findings in bring-add, spanning Policy Violation, Permissions Manifest and Supply Chain.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for bring-add

Resolve policy violations
bring-add 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.
Update and pin dependencies
bring-add depends on packages with supply-chain risk. Pin every dependency to an exact version, update packages with known CVEs to patched releases, and re-audit after each change. ClawSecure checks every dependency against known CVE databases.
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

oh-my-claudecodeScore 80/100openclaw-dashboard-repoScore 95/100api-gatewayScore 91/100opencode-auto-continueScore 90/100@fazaboa/opencode-auto-continueScore 95/100

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