encrata-cli@0.12.0
Encrata CLI — intelligence lookups from your terminal
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe inspected installer and launcher implement a package-aligned native CLI installation, with no concrete malicious behavior or lifecycle self-dependency. Missing artifact verification limits assurance but does not establish an attack; the scanner's transport-verification claim is unsupported by the HTTPS implementation.
Decision evidence
public snapshot- package.json runs install.js after installation and declares no runtime dependencies.
- install.js downloads a versioned platform archive from the Encratahq/encrata-cli GitHub releases using HTTPS.
- The installer follows HTTP redirects through HTTPS requests; it does not disable TLS verification.
- The installer copies the executable into its package directory and removes extraction files.
- bin/encrata executes the installed binary when the user invokes the CLI, forwarding command arguments.
- Downloaded archives lack checksum or signature verification, and the remote executable's behavior is outside this snapshot.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time source downloads a native archive from a fixed external host without transport verification, extracts it, and installs an executable payload.
package.jsonView on unpkg · L2Findings
Affected versions and remediation
This report applies to encrata-cli@0.12.0.
See all versions of encrata-cli for other recorded verdicts.
- Review the evidence and your use of encrata-cli@0.12.0 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.