@sciagent/cli@1.0.84
SciAgent CLI - AI Research Assistant
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe source establishes a serious unconsented staged-payload delivery and execution chain, but does not itself prove the downloaded artifacts perform malicious actions or mutate a foreign AI-agent control surface. This warrants a warning rather than a publish block under the stated boundary.
Decision evidence
public snapshot- `package.json` runs `scripts/postinstall.js` automatically.
- `scripts/postinstall.js` downloads unsigned >10MB platform binaries during postinstall.
- `scripts/postinstall.js` fetches and extracts a CodeBuddy wheel, then globally installs `@tencent-ai/codebuddy-code` as fallback.
- `bin/sciagent.js` re-downloads a missing or version-mismatched binary and executes it via `spawn`.
- No checksum, signature, or pinned artifact digest validates downloaded executables.
- Inspected code contains no credential harvesting or outbound file/env exfiltration.
- No `eval`, `Function`, hidden process, AI-agent configuration write, or destructive broad filesystem action was found.
- Writes are limited to package-owned SciAgent directories, temporary SDK files, and a global npm dependency.
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 unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/sciagent.jsFindings
Affected versions and remediation
This report applies to @sciagent/cli@1.0.84.
See all versions of @sciagent/cli for other recorded verdicts.
- Review the evidence and your use of @sciagent/cli@1.0.84 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.