@sciagent/cli@1.1.33
SciAgent CLI - AI Research Assistant
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe source establishes a concrete automatic remote-payload installation and later execution path, but no direct malicious objective is visible in the inspected JavaScript. This warrants a warning rather than a block under the stated lifecycle policy.
Decision evidence
public snapshot- package.json runs scripts/postinstall.js automatically.
- postinstall downloads large native binaries from JiHuLab/release server into ~/.sciagent/bin.
- postinstall fetches a CodeBuddy wheel, extracts its executable, and falls back to npm install -g.
- bin/sciagent.js later executes the downloaded sciagent binary and auto-updates it.
- Downloaded artifacts have only size checks; no checksum or signature verification.
- No source evidence of credential or environment harvesting.
- No exfiltration, destructive broad filesystem actions, or AI-agent control-surface writes found.
- Process termination is limited to the package's named sciagent process and requires an update path.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @sciagent/cli@1.1.33.
See all versions of @sciagent/cli for other recorded verdicts.
- Review the evidence and your use of @sciagent/cli@1.1.33 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.