@dptech-corp/bohr-cli@2.5.22
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe postinstall hook deliberately replaces a foreign global command link, creating a concrete command-hijack risk. It is not a confirmed AI-agent control-surface attack or install-time exfiltration, so warning rather than blocking is appropriate.
Decision evidence
public snapshot- package.json runs postinstall via install.js.
- install.js invokes global npm-bin discovery.
- install.js deletes an existing global bohr link when it resolves elsewhere.
- install.js replaces it with a symlink to this package's run.js.
- The lifecycle script contains no network or credential collection.
- Replacement is limited to the bohr command name.
- run.js only selects and executes a bundled platform binary on explicit CLI use.
Source & flagged code
3 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 @dptech-corp/bohr-cli@2.5.22.
See all versions of @dptech-corp/bohr-cli for other recorded verdicts.
- Review the evidence and your use of @dptech-corp/bohr-cli@2.5.22 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.