@dptech-corp/bohr-cli@2.6.61
CLI tool for Bohrium scientific computing platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package automatically delivers executable payloads during installation, creating a supply-chain risk. Its writes are package-owned and the inspected source does not establish malicious collection, persistence outside that area, or control-surface hijacking.
Decision evidence
public snapshot- The install lifecycle runs postinstall.js automatically.
- The lifecycle fetches release metadata and binaries from vendor endpoints, with redirects followed.
- Downloaded companion executables are made executable and placed under the package-owned .bohr tool directory.
- The trisol server can be overridden through an environment variable.
- The inspected JavaScript does not harvest credentials, environment values, or unrelated files.
- No self-dependency, shell command construction, eval, or broad project configuration write is present.
- The launcher only resolves and executes the matching platform package when the user invokes bohr.
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.61.
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.61 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.