base_parts_ai@1.0.61
jaskle base_parts_ai
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI performs an unprompted forced global self-update using a version selected by a remote response, creating a concrete remote code execution risk. The update is triggered by user-invoked CLI commands, so the inspected behavior supports a warning rather than a publish block.
Decision evidence
public snapshot- Running the jcx command calls fetchConfig before its selected configuration action.
- fetchConfig downloads configuration from jai.jaskle.cn and accepts a server-provided version.
- The update confirmation is hardcoded to yes, with the interactive confirmation commented out.
- The updater downloads a package archive and runs a forced global npm install from it.
- The package exposes jcx as a command-line entry point; the update chain runs when a CLI command is invoked, not from an npm lifecycle hook.
- The reviewed Claude settings setup and ucx account-directory behavior do not establish an attack.
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.61.
See all versions of base_parts_ai for other recorded verdicts.
- Review the evidence and your use of base_parts_ai@1.0.61 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.