← Back to Scanner

opencode-auto-continue Security Audit Report

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

opencode-auto-continue is an AI agent skill, created by hjzccc and published at hjzccc/opencode-auto-continue. ClawSecure audited opencode-auto-continue across 10 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 2 findings concentrate in Permissions Manifest and Supply Chain, including Missing config.json - agent may not be properly configured and Unpinned dependency: bun-types (version: latest) - pin to…. None were rated high or critical severity.

Is opencode-auto-continue safe?

ClawSecure audited opencode-auto-continue and assigned a security score of 90/100 (Safe), identifying 2 findings across Permissions Manifest and Supply Chain. Review the findings below before installing.

What did ClawSecure find in opencode-auto-continue?

ClawSecure identified 2 findings in opencode-auto-continue, concentrated in Permissions Manifest and Supply Chain. The most severe include Missing config.json - agent may not be properly configured and Unpinned dependency: bun-types (version: latest) - pin to….

How was opencode-auto-continue audited?

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

What does a score of 90 mean?

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

ClawSecure detected 2 security findings in opencode-auto-continue, spanning Permissions Manifest and Supply Chain.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for opencode-auto-continue

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
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.
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

How to Secure an MCP Server: The 2026 Guide→What Is MCP Security? Model Context Protocol Explained→AI Agent Supply Chain Attacks: How Dependencies Become Weapons→

Related AI Agent Security Audits

@fazaboa/opencode-auto-continueScore 95/100shodan-skillScore 90/100oh-my-claudecodeScore 80/100api-gatewayScore 91/100clawdhubScore 85/100

Scanned on August 25, 2026. 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