registry / @dptech-corp/bohr-cli / 2.7.22
@dptech-corp/bohr-cli@2.7.22
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe lifecycle hook’s automatic downloads are package-aligned companion tools, and the source requires a matching SHA-256 before installation. The launcher runs the vendor’s platform-specific binary; no malicious behavior was found in the inspected source.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its postinstall hook; invoking `bohr` starts the matching platform binary.
Impact
No malicious effect was identified in the inspected source.
Mechanism
The hook installs verified companion executables but does not launch them. The launcher resolves the corresponding same-vendor optional package and forwards arguments to its binary.
AI rationale
The lifecycle hook’s automatic downloads are package-aligned companion tools, and the source requires a matching SHA-256 before installation. The launcher runs the vendor’s platform-specific binary; no malicious behavior was found in the inspected source.
Evidence
~/.bohr/tools/trisol/current~/.bohr/tools/wenyon/current
Network endpoints2
trisol.dp.techwenyon.dp.tech
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a postinstall hook and a `bohr` launcher.
- run.js resolves the matching platform binary from a same-vendor optional package and forwards the caller’s arguments to it.
- postinstall.js fetches companion-tool metadata from the vendor’s Trisol and Wenyon services and targets `~/.bohr/tools`.
- The hook rejects unusable hashes and checks the downloaded file’s SHA-256 before installing it as an executable.
- The inspected postinstall path installs the companion tools but does not launch them.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg8"scripts": {
"postinstall": "node postinstall.js"
},
"keywords": [
"bohrium",
"sci
Low
Suspicious Lifecycle Evidence
package.json defines a postinstall hook and a `bohr` launcher.
package.jsonView on unpkg · L8run.js#virtual:normalized:round1View file
Findings
2 High4 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedrun.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencerun.js
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.7.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.7.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.