← Back to Scanner

@fazaboa/opencode-auto-continue Security Audit Report

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

@fazaboa/opencode-auto-continue is an AI agent skill, created by PedroLuisBrilhadori and published at PedroLuisBrilhadori/opencode-auto-continue. ClawSecure audited @fazaboa/opencode-auto-continue across 27 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 55/100 (Medium Risk). The 3 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in vitest@3.0.0: When Vitest UI server is… and Vulnerability in vitest@3.0.0: Vitest allows Remote Code…. 2 were rated high or critical severity.

Is @fazaboa/opencode-auto-continue safe?

ClawSecure audited @fazaboa/opencode-auto-continue and assigned a security score of 55/100 (Medium Risk), identifying 3 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in @fazaboa/opencode-auto-continue?

ClawSecure identified 3 findings in @fazaboa/opencode-auto-continue, concentrated in Supply Chain and Permissions Manifest. 2 were rated high or critical severity. The most severe include Vulnerability in vitest@3.0.0: When Vitest UI server is… and Vulnerability in vitest@3.0.0: Vitest allows Remote Code….

How was @fazaboa/opencode-auto-continue audited?

ClawSecure ran @fazaboa/opencode-auto-continue through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 27 files from PedroLuisBrilhadori/opencode-auto-continue.

What does a score of 55 mean?

ClawSecure assigned @fazaboa/opencode-auto-continue a security score of 55/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 @fazaboa/opencode-auto-continue

ClawSecure detected 3 security findings in @fazaboa/opencode-auto-continue, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @fazaboa/opencode-auto-continue

Update and pin dependencies
@fazaboa/opencode-auto-continue 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

@modelcontextprotocol/serversScore 50/100gitlab-cli-skillsScore 55/100xlsxScore 63/100docxScore 68/100skill-vetter-v2Score 70/100

Scanned on August 28, 2026. @fazaboa/opencode-auto-continue 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