← Back to Scanner

@mohtasham/md-to-docx Security Audit Report

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

@mohtasham/md-to-docx is an AI agent skill, created by Mohtasham and published at MohtashamMurshid/md-to-docx. ClawSecure audited @mohtasham/md-to-docx across 60 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 0/100 (High Risk). The 23 findings concentrate in Supply Chain, ReDoS and Code Injection, including Vulnerability in next@15.5.22: Next.js: Unauthenticated… and Vulnerability in next@15.5.22: Next.js: Unauthenticated…. 17 were rated high or critical severity.

Is @mohtasham/md-to-docx safe?

ClawSecure audited @mohtasham/md-to-docx and assigned a security score of 0/100 (High Risk), identifying 23 findings across Supply Chain and ReDoS. Review the findings below before installing.

What did ClawSecure find in @mohtasham/md-to-docx?

ClawSecure identified 23 findings in @mohtasham/md-to-docx, concentrated in Supply Chain, ReDoS and Code Injection. 17 were rated high or critical severity. The most severe include Vulnerability in next@15.5.22: Next.js: Unauthenticated… and Vulnerability in next@15.5.22: Next.js: Unauthenticated….

How was @mohtasham/md-to-docx audited?

ClawSecure ran @mohtasham/md-to-docx through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 60 files from MohtashamMurshid/md-to-docx.

What does a score of 0 mean?

ClawSecure assigned @mohtasham/md-to-docx a security score of 0/100, placing it in the High Risk range. This is driven by 23 findings led by Supply Chain that should be addressed before 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 @mohtasham/md-to-docx

ClawSecure detected 23 security findings in @mohtasham/md-to-docx, spanning Supply Chain, ReDoS, Code Injection and Permissions Manifest.

Showing the 12 highest-severity of 23 findings. The full interactive list appears below.

3-Layer Audit Protocol

Security Recommendations for @mohtasham/md-to-docx

Update and pin dependencies
@mohtasham/md-to-docx 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.
Fix ReDoS-prone patterns
@mohtasham/md-to-docx contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
Eliminate dynamic code execution
@mohtasham/md-to-docx 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.

Related Security Research

AI Agent Supply Chain Attacks: How Dependencies Become WeaponsBeyond Static Scans: Why ClawSecure Verifies Agentic Intent

Related AI Agent Security Audits

anysearchScore 0/100ai-ppt-generatorScore 0/100capability-evolverScore 0/100capability-evolverScore 0/100youtube-summarizeScore 0/100

Scanned on September 11, 2026. @mohtasham/md-to-docx 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