← Back to Scanner

@martian-engineering/lossless-claw Security Audit Report

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

@martian-engineering/lossless-claw is an AI agent skill, created by Josh Lehman <josh@martian.engineering> and published at martian-engineering/lossless-claw. ClawSecure audited @martian-engineering/lossless-claw across 50 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 2 findings concentrate in Permissions Manifest and Code Injection, including Potentially dangerous code pattern detected: exec\( and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is @martian-engineering/lossless-claw safe?

ClawSecure audited @martian-engineering/lossless-claw and assigned a security score of 85/100 (Safe), identifying 2 findings across Permissions Manifest and Code Injection. Review the findings below before installing.

What did ClawSecure find in @martian-engineering/lossless-claw?

ClawSecure identified 2 findings in @martian-engineering/lossless-claw, concentrated in Permissions Manifest and Code Injection. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: exec\( and Missing config.json - agent may not be properly configured.

How was @martian-engineering/lossless-claw audited?

ClawSecure ran @martian-engineering/lossless-claw through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 50 files from martian-engineering/lossless-claw.

What does a score of 85 mean?

ClawSecure assigned @martian-engineering/lossless-claw 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 @martian-engineering/lossless-claw

ClawSecure detected 2 security findings in @martian-engineering/lossless-claw, spanning Permissions Manifest and Code Injection.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @martian-engineering/lossless-claw

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.
Eliminate dynamic code execution
@martian-engineering/lossless-claw evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
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 GuideWhat Is MCP Security? Model Context Protocol ExplainedWhy Generic Scanners Fail at AI Agent Security

Related AI Agent Security Audits

aitorScore 81/1003f5bb9462d7cb920Score 75/100b4abd97bcb77151aScore 75/100clawdhubScore 75/100mission-controlScore 83/100

Scanned on June 2, 2026. @martian-engineering/lossless-claw 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