@shendu-sdt/sd-zentao-cli
SD internal ZenTao CLI for bug, task, and workhour workflows.
This report shows the evidence for @shendu-sdt/sd-zentao-cli@0.1.14, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection confirms a postinstall hook mutates broad/foreign AI-agent control surfaces without requiring an explicit setup command, which matches the firewall block policy. The rest of the CLI appears package-aligned and does not show credential exfiltration or remote payload execution, but the install-time AI control-surface write is sufficient to block.
Decision evidence
public snapshot- package.json defines postinstall: node scripts/install-ai-skill.mjs
- scripts/install-ai-skill.mjs copies SKILL.md into broad AI-agent directories under ~/.codex, ~/.agents, ~/.claude, ~/.cursor, ~/.gemini, etc.
- postinstall also removes old zentao-cli skill directories across the same agent surfaces
- SKILL.md instructs agents to prefer szt and guides bug/workhour write workflows
- No credential exfiltration found; saved ZenTao credentials stay in ~/.szt-cli/config.json with 0600 permissions
- Network use is ZenTao-aligned via configured URL/default https://pm.sdpjw.com/index.php and REST/legacy API calls
- child_process use is limited to invoking install-ai-skill.mjs and retrying the same CLI after relogin; git execFile supports user-invoked work scan
- No eval/vm/dynamic remote payload loading found
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @shendu-sdt/sd-zentao-cli@0.1.14.
The versions list below shows the verdict for each recorded version.
- Avoid installing @shendu-sdt/sd-zentao-cli@0.1.14. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.