@dptech-corp/bohr-cli@2.6.57
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource shows a first-party CLI: postinstall fetches hashed companion tools from dp.tech into ~/.bohr/tools, and run.js launches the matching optional platform binary. Scanner malware-similarity and runtime-install labels come from that installer pattern and an error hint, not a hidden attack.
Decision evidence
public snapshot- postinstall.js runs on npm install and downloads companion binaries into the user home directory.
- run.js is the bohr launcher and executes a native binary from an optional platform package.
- package.json declares a postinstall lifecycle script.
- Downloads use vendor hosts wenyon.dp.tech and trisol.dp.tech, check SHA-256, and write only under ~/.bohr/tools.
- run.js resolves same-version @dptech-corp/bohr-cli platform packages; the npm install string is an error hint, not a runtime installer.
- No credential harvest, eval, agent-config writes, obfuscation, or a runtime self-dependency on this package name.
Source & flagged code
10 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.
postinstall.jsFindings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.6.57.
See all versions of @dptech-corp/bohr-cli for other recorded verdicts.
- Review the evidence and your use of @dptech-corp/bohr-cli@2.6.57 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.