registry / @dptech-corp/bohr-cli / 2.7.11
@dptech-corp/bohr-cli@2.7.11
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found an install-time companion-tool setup flow and a CLI launcher consistent with the package’s stated purpose. The inspected evidence does not establish an attack surface warranting a warning or block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install triggers the package’s postinstall script.
Impact
The inspected behavior supports the package’s CLI functionality; no malicious effect was established.
Mechanism
The script retrieves companion tool metadata and artifacts, then installs managed files; the launcher spawns the platform-specific Bohr binary when invoked.
AI rationale
Source inspection found an install-time companion-tool setup flow and a CLI launcher consistent with the package’s stated purpose. The inspected evidence does not establish an attack surface warranting a warning or block.
Evidence
~/.bohr/tools/wenyon/current~/.bohr/tools/trisol/current
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs postinstall.js during installation.
- run.js is a launcher that spawns the platform-specific Bohr binary with caller arguments.
- postinstall.js fetches companion CLI artifacts and checks downloaded files as part of installation.
- The postinstall entry calls main() and handles failures without aborting npm installation.
Evidence against
- The inspected source shows no credential collection, secret transmission, or unrelated consumer configuration changes.
- The fetched companion tools are installed under the user’s .bohr tools directory; no execution of them during postinstall was identified.
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",
"scientific-computi
Low
Suspicious Lifecycle Evidence
package.json runs postinstall.js during installation.
package.jsonView on unpkg · L8run.js#virtual:normalized:round1View file
Findings
3 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedrun.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltarun.js
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
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.7.11.
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.11 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.