← Back to Scanner

@drkraft/basecamp-cli Security Audit Report

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

@drkraft/basecamp-cli is an AI agent skill, created by drkraft and published at openclaw/skills. ClawSecure audited @drkraft/basecamp-cli across 58 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Policy Violation, Permissions Manifest and Supply Chain, including Vulnerability in @modelcontextprotocol/sdk@1.25.3:... and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is @drkraft/basecamp-cli safe?

ClawSecure audited @drkraft/basecamp-cli and assigned a security score of 85/100 (Safe), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in @drkraft/basecamp-cli?

ClawSecure identified 3 findings in @drkraft/basecamp-cli, concentrated in Policy Violation, Permissions Manifest and Supply Chain. 1 was rated high or critical severity. The most severe include Vulnerability in @modelcontextprotocol/sdk@1.25.3:... and Missing config.json - agent may not be properly configured.

How was @drkraft/basecamp-cli audited?

ClawSecure ran @drkraft/basecamp-cli through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 58 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned @drkraft/basecamp-cli a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. 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 @drkraft/basecamp-cli

ClawSecure detected 3 security findings in @drkraft/basecamp-cli, spanning Policy Violation, Permissions Manifest and Supply Chain.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @drkraft/basecamp-cli

Resolve policy violations
@drkraft/basecamp-cli 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
@drkraft/basecamp-cli 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 Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

devops-mainScore 75/100TestFilesScore 95/100devops-mainScore 75/100devops-mainScore 75/100redditScore 80/100

Scanned on February 7, 2026. @drkraft/basecamp-cli 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