← Back to Scanner

vibes Security Audit Report

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

vibes is an AI agent skill, created by binora and published at binora/vibes. ClawSecure audited vibes across 13 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 3 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in @modelcontextprotocol/sdk@1.0.0: Anthropic's MCP... and Vulnerability in @modelcontextprotocol/sdk@1.0.0: Model Context.... 2 were rated high or critical severity.

Is vibes safe?

ClawSecure audited vibes and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in vibes?

ClawSecure identified 3 findings in vibes, concentrated in Supply Chain and Permissions Manifest. 2 were rated high or critical severity. The most severe include Vulnerability in @modelcontextprotocol/sdk@1.0.0: Anthropic's MCP... and Vulnerability in @modelcontextprotocol/sdk@1.0.0: Model Context....

How was vibes audited?

ClawSecure ran vibes through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 13 files from binora/vibes.

What does a score of 75 mean?

ClawSecure assigned vibes a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Supply Chain that warrant review before production use. 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 vibes

ClawSecure detected 3 security findings in vibes, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for vibes

Update and pin dependencies
vibes 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.
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

AI Agent Supply Chain Attacks: How Dependencies Become WeaponsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

MiroFishScore 80/100ui-ux-pro-max-skillScore 75/100antigravity-awesome-skillsScore 75/100GitNexusScore 75/100zeroclawScore 85/100

Scanned on May 5, 2026. vibes 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