← Back to Scanner

@soimy/dingtalk Security Audit Report

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

@soimy/dingtalk is an AI agent skill, created by YM Shen <soimy@163.com> (http://github.com/soimy) and published at soimy/openclaw-channel-dingtalk. ClawSecure audited @soimy/dingtalk across 103 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Moderate). The 4 findings concentrate in ReDoS, Code Injection and Permissions Manifest, 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 @soimy/dingtalk safe?

ClawSecure audited @soimy/dingtalk and assigned a security score of 75/100 (Moderate), identifying 4 findings across ReDoS and Code Injection. Review the findings below before installing.

What did ClawSecure find in @soimy/dingtalk?

ClawSecure identified 4 findings in @soimy/dingtalk, concentrated in ReDoS, Code Injection and Permissions Manifest. 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 @soimy/dingtalk audited?

ClawSecure ran @soimy/dingtalk through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 103 files from soimy/openclaw-channel-dingtalk.

What does a score of 75 mean?

ClawSecure assigned @soimy/dingtalk a security score of 75/100, placing it in the Moderate range. This reflects 4 findings led by ReDoS 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 @soimy/dingtalk

ClawSecure detected 4 security findings in @soimy/dingtalk, spanning ReDoS, Code Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @soimy/dingtalk

Fix ReDoS-prone patterns
@soimy/dingtalk 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
@soimy/dingtalk 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.
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

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→

Related AI Agent Security Audits

GitNexusScore 75/100openclawScore 75/100antigravity-awesome-skillsScore 75/100zeroclawScore 85/100superpowersScore 85/100

Scanned on September 18, 2026. @soimy/dingtalk 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