@dptech-corp/bohr-cli@2.5.25
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe install hook performs a concrete destructive global command replacement. It does not establish credential theft, exfiltration, remote payload execution, or foreign AI-agent control-surface mutation, so blocking is not warranted.
Decision evidence
public snapshot- package.json runs postinstall: node install.js.
- install.js runs npm bin -g during installation.
- install.js deletes an existing global bohr entry when it resolves elsewhere.
- install.js replaces that entry with a symlink to this package's run.js.
- run.js only selects and executes the bundled platform binary with user arguments.
- install.js has no network, credential-harvesting, eval, or agent-config logic.
- No network activity is present in the install-time JavaScript.
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.25.
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.25 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.