jpcode-cli
DEPRECATED: este paquete se movio. Instala @soyjuanpiece/jpcode (npm i -g @soyjuanpiece/jpcode) - mismo comando jpcode, motor opencode actualizado
This report shows the evidence for jpcode-cli@1.18.37, the only known version.
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe automatic lifecycle hook writes an unrestricted agent configuration outside the package into a global AI-agent configuration directory. Existing-file preservation and an opt-out do not establish consent for this default mutation.
Decision evidence
public snapshot- package.json automatically runs postinstall.mjs during installation.
- The postinstall script copies bundled agent and command files into the user's global OpenCode configuration.
- The installed auto agent grants all permissions and states that edits, shell access, and external directories are pre-approved.
- The installer preserves an existing file and offers an environment-variable opt-out.
- No network endpoint or credential collection was found in the inspected install path.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json automatically runs postinstall.mjs during installation.
package.jsonView on unpkg · L3Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to jpcode-cli@1.18.37.
The versions list below shows the verdict for each recorded version.
- Avoid installing jpcode-cli@1.18.37. 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.