@dptech-corp/bohr-cli@2.7.15
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic companion executable installation creates a real but package-aligned payload supply-chain risk: the hook obtains both the binary and its expected hash through the release service. Source inspection shows no concrete attack behavior, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest runs postinstall.js automatically during installation.
- The hook downloads companion executables into the user's .bohr tools directory.
- The trisol download and expected hash come from the same configured release service; integrity is checked before installation.
- run.js launches the installed platform-specific Bohr binary.
- The hook does not execute the downloaded companion immediately; the inspected path downloads, checks, and installs it.
- The hook's inspected companion setup targets Bohr's own tool directory and has no credential collection or unrelated consumer-project mutation.
Source & flagged code
5 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 unpkgThe manifest runs postinstall.js automatically during installation.
package.jsonView on unpkg · L5Findings
Affected versions and remediation
This report applies to @dptech-corp/bohr-cli@2.7.15.
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.15 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.