@boxes-dev/dvb@1.0.1039
AI security review
scanned · by lpm-firewall-aiThe package has no harmful install-time behavior, but its normal CLI path downloads and executes a latest runtime selected remotely without a pinned release or integrity check visible in this source. That concrete update capability warrants a warning, not a malware block.
Decision evidence
public snapshot- package.json defines a postinstall hook, but the hook only prints a next-step message for global installs.
- The CLI fetches the latest @boxes-dev/dvb-runtime manifest from the npm registry and accepts its tarball URL.
- It downloads and extracts that tarball into the user's runtime directory, then starts binaries from the staged runtime.
- Ordinary CLI launches start a detached background updater.
- No credential harvesting, data export, eval, shell execution, or destructive consumer-project mutation was found in the inspected package files.
- The install hook does not download or execute code; it only writes a message.
- deploy.boxes.dev
- registry.npmjs.org
Findings
1 high · 6 medium · 5 lowWhere they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
package.json1 high · 2 mediumShow all 12 findings
package.json3 findingsSource & flagged code
3 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgShared scanner record · 2 findings · 1 line
package.json defines a postinstall hook, but the hook only prints a next-step message for global installs.
package.jsonView on unpkg · L23Code excerpt · 5 lines
Affected versions and remediation
This report applies to @boxes-dev/dvb@1.0.1039.
See all versions of @boxes-dev/dvb for other recorded verdicts.
- Review the evidence and your use of @boxes-dev/dvb@1.0.1039 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.