Scan Report
20 /100
crawdaddy
Autonomous security scanner for post-quantum cryptography readiness, smart contracts, and agent credential exposure
This is a pure-documentation skill bundle with no executable code whatsoever — it claims autonomous security scanning capabilities in SKILL.md but contains zero scripts or implementation files, making it incapable of performing any of its advertised functions.
Safe to install
Do not trust this skill to perform any actual security scanning. It has no code; it is purely marketing documentation. If you need genuine post-quantum security analysis, use a properly implemented tool.
Findings 3 items
| Severity | Finding | Location |
|---|---|---|
| Medium | Zero executable code despite autonomous scanning claims Doc Mismatch | SKILL.md:1 |
| Low | No allowed-tools declaration in _meta.json Doc Mismatch | _meta.json |
| Low | Embedded monetization in documentation Doc Mismatch | SKILL.md:53 |
| Resource | Declared | Inferred | Status | Evidence |
|---|---|---|---|---|
| Filesystem | NONE | NONE | — | No scripts, no file access code, no Read/Write tool usage |
| Network | NONE | NONE | — | No WebFetch, curl, or HTTP client code present |
| Shell | NONE | NONE | — | No Bash calls, no subprocess, no shell scripts |
| Environment | NONE | NONE | — | No os.environ access or env file present |
| Skill Invoke | NONE | NONE | — | No inter-skill invocation code |
| Clipboard | NONE | NONE | — | No clipboard access code |
| Browser | NONE | NONE | — | No browser automation code |
| Database | NONE | NONE | — | No database connectivity code |
3 findings
Medium External URL 外部 URL
https://quantumshieldlabs.dev/agent/ README.md:23 Medium Wallet Address 加密货币钱包地址
0x25B50fEd69175e474F9702C0613413F8323809a8 SKILL.md:58 Info Email 邮箱地址
[email protected] README.md:22 File Tree
3 files · 5.2 KB · 164 lines Markdown 2f · 137L
JSON 1f · 27L
├─
package.json
JSON
├─
README.md
Markdown
└─
SKILL.md
Markdown
Security Positives
✓ No executable code means no direct attack surface — the skill cannot perform any harmful actions
✓ No sensitive file access, environment variable reads, or credential harvesting code
✓ No network requests, external IP connections, or data exfiltration mechanisms
✓ No obfuscation techniques (base64, eval, encoding) present
✓ No supply chain risk — no dependencies, no package manager files with runtime code
✓ No persistence mechanisms (cron, startup scripts, backdoors)