← 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 68 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 35/100 (High Risk). The 6 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in form-data@4.0.0: form-data uses unsafe… and Vulnerability in axios@1.6.0: Axios is Vulnerable to Denial…. 5 were rated high or critical severity.

Is @soimy/dingtalk safe?

ClawSecure audited @soimy/dingtalk and assigned a security score of 35/100 (High Risk), identifying 6 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in @soimy/dingtalk?

ClawSecure identified 6 findings in @soimy/dingtalk, concentrated in Supply Chain and Permissions Manifest. 5 were rated high or critical severity. The most severe include Vulnerability in form-data@4.0.0: form-data uses unsafe… and Vulnerability in axios@1.6.0: Axios is Vulnerable to Denial….

How was @soimy/dingtalk audited?

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

What does a score of 35 mean?

ClawSecure assigned @soimy/dingtalk a security score of 35/100, placing it in the High Risk range. This is driven by 6 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 @soimy/dingtalk

ClawSecure detected 6 security findings in @soimy/dingtalk, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @soimy/dingtalk

Update and pin dependencies
@soimy/dingtalk 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.
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

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

Related AI Agent Security Audits

mission-controlScore 33/100mission-controlScore 33/100@martian-engineering/lossless-clawScore 25/100@martian-engineering/lossless-clawScore 25/100ClawSecScore 45/100

Scanned on March 3, 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