Scan Report
15 /100
interactive-architecture-diagram
AI automation drawing and complex information visualization tool based on ContextWeave
This is a legitimate diagram generation client that sends user requests to an external API. While there are minor concerns about a hardcoded API key and an undeclared API host, the core functionality is straightforward and documented.
Safe to install
Consider replacing the hardcoded API key with a proper error message and documenting the bpjwmsdb.com endpoint. Otherwise safe to use for its stated purpose.
Findings 2 items
| Severity | Finding | Location |
|---|---|---|
| Low | Hardcoded default API key in source Credential Theft | scripts/cw_client.cjs:21 |
| Low | Undeclared API host in allowlist Doc Mismatch | scripts/cw_client.cjs:45 |
| Resource | Declared | Inferred | Status | Evidence |
|---|---|---|---|---|
| Filesystem | READ | READ | ✓ Aligned | Reads input_file parameter path |
| Filesystem | WRITE | WRITE | ✓ Aligned | Writes .cw files and request files to cwd |
| Network | READ | WRITE | ✓ Aligned | POSTs data to API, declared as '后端地址' without explicit READ/WRITE distinction |
| Shell | WRITE | WRITE | ✓ Aligned | Executes 'node scripts/*.cjs' via Bash |
| Environment | READ | READ | ✓ Aligned | Reads CONTEXTWEAVE_MCP_API_KEY and CONTEXTWEAVE_EDITOR_PROTOCOL |
2 findings
Medium External URL 外部 URL
https://pptx.chenxitech.site SKILL.md:189 Medium External URL 外部 URL
https://api.contextweave.site cwmcp_config.example.json:2 File Tree
9 files · 31.3 KB · 855 lines JavaScript 6f · 648L
Markdown 1f · 192L
JSON 2f · 15L
├─
▾
scripts
│ ├─
cw_client.cjs
JavaScript
│ ├─
edit_contextweave.cjs
JavaScript
│ ├─
export_contextweave_code.cjs
JavaScript
│ ├─
export_session_asset.cjs
JavaScript
│ ├─
generate_contextweave.cjs
JavaScript
│ └─
import_contextweave_code.cjs
JavaScript
├─
_meta.json
JSON
├─
cwmcp_config.example.json
JSON
└─
SKILL.md
Markdown
Security Positives
✓ Path traversal protection via validateSafePath() rejects paths outside cwd
✓ Host allowlist restricts API endpoints to known domains
✓ No credential scanning or harvesting from sensitive paths (~/.ssh, ~/.aws, .env)
✓ No obfuscation techniques (base64, eval) observed
✓ No suspicious network behavior like direct IP connections
✓ No persistence mechanisms (cron, startup hooks) installed
✓ Input files validated for existence before reading