@boxes-dev/dvb@1.0.1026
AI security review
scanned · by lpm-firewall-aiThe package implements a user-triggered, persistent remote runtime-update and execution mechanism. That is a dangerous capability with unresolved supply-chain exposure, but the inspected source does not establish malicious intent or an active install-time attack.
Decision evidence
public snapshot- The manifest exposes three executable command-line entrypoints and a postinstall hook.
- The postinstall hook only prints a next-step message for global installs.
- The launcher fetches a latest runtime manifest from the npm registry.
- It spawns the fetched runtime as a child process when the command is invoked.
- A normal command invocation starts a detached background updater daemon.
- The automatic install hook shown only writes a message and does not perform a mutation or download.
- The remote update path is activated by invoking the package command, not by installation.
- 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
The manifest exposes three executable command-line entrypoints and a postinstall hook.
package.jsonView on unpkg · L9Code excerpt · 8 lines
Affected versions and remediation
This report applies to @boxes-dev/dvb@1.0.1026.
See all versions of @boxes-dev/dvb for other recorded verdicts.
- Review the evidence and your use of @boxes-dev/dvb@1.0.1026 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.