← 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 101 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 4 findings concentrate in ReDoS, 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 @soimy/dingtalk safe?

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

What did ClawSecure find in @soimy/dingtalk?

ClawSecure identified 4 findings in @soimy/dingtalk, concentrated in ReDoS, 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 @soimy/dingtalk audited?

ClawSecure ran @soimy/dingtalk through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 101 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 Medium Risk 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, Permissions Manifest and Code Injection.

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.
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
@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.
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→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

19af8eafb16b72f6Score 75/100clawdhubScore 75/10019af8eafb16b72f6Score 75/10025937fcc251c4ccbScore 85/100c81972687d0e5a06Score 75/100

Scanned on June 4, 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