base_parts_ai@1.0.58
jaskle base_parts_ai
AI Security Review
scanned 3d ago · by lpm-firewall-aiNo npm lifecycle hook is declared, and the risky behavior is reachable through CLI use. The silent update and remote overwrite of global agent instructions leave concrete residual risk, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- package.json declares no npm lifecycle hook; `__postinstall` is a custom script entry.
- Running the jcx command calls fetchConfig before its selected configuration module.
- When the server reports a newer version, the update branch sets confirmation to yes without asking the user.
- The updater installs a versioned package tarball globally and reruns the CLI.
- After a Codex channel is selected, the program fetches remote ai_tip text from jai.jaskle.cn.
- That fetched text is written to the user's global Codex AGENTS.md after channel configuration.
Source & flagged code
7 flagged · loading sourceRuntime or CLI source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/jcx.jsView on unpkgFindings
Affected versions and remediation
This report applies to base_parts_ai@1.0.58.
See all versions of base_parts_ai for other recorded verdicts.
- Review the evidence and your use of base_parts_ai@1.0.58 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.