registry / @dptech-corp/bohr-cli / 2.7.3
@dptech-corp/bohr-cli@2.7.3
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found a vendor-aligned companion-tool installer with SHA-256 validation, plus a launcher for the platform-specific CLI binary. The scanner's lifecycle and network signals correspond to these behaviors; no concrete attack behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation triggers postinstall; invoking bohr launches the platform-specific optional package binary.
Impact
No malicious effect was established from the inspected source; the CLI and companion tools are installed and launched as intended.
Mechanism
The postinstall retrieves tool metadata and binaries from vendor services and verifies the downloaded file against the expected SHA-256 before installation.
AI rationale
Source inspection found a vendor-aligned companion-tool installer with SHA-256 validation, plus a launcher for the platform-specific CLI binary. The scanner's lifecycle and network signals correspond to these behaviors; no concrete attack behavior was identified.
Evidence
~/.bohr/tools/wenyon~/.bohr/tools/trisol
Network endpoints2
wenyon.dp.techtrisol.dp.tech
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines postinstall to run postinstall.js.
- The postinstall installs companion tools under the user's .bohr directory and fetches them from the vendor's wenyon.dp.tech and trisol.dp.tech services.
- Installation requires a valid SHA-256 value and removes a downloaded file when its hash does not match.
- run.js resolves a platform-specific optional package and launches its binary with the caller's arguments.
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",
"scientific-computing",
"cli",
"paper-sea
Low
Suspicious Lifecycle Evidence
package.json defines postinstall to run postinstall.js.
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.3.
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.3 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.