@boxes-dev/dvb@1.0.1029
AI security review
scanned · by lpm-firewall-aiThe package contains a user-triggered, persistent updater that stages remotely supplied code without a visible integrity or destination control. Its install hook is limited to a global-install message, so the evidence supports a warning rather than a block.
Decision evidence
public snapshot- The package declares a postinstall hook, but its hook only prints a message during global installation.
- Running the dvb command automatically starts a detached background updater.
- The updater obtains a runtime manifest from the npm registry and accepts its tarball field.
- The updater downloads and extracts that tarball without an integrity value or destination restriction shown in the inspected code.
- The install hook does not itself modify files, start processes, or contact the network.
- The observed registry endpoint is package-aligned, and no credential collection or exfiltration was found.
- 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 package declares a postinstall hook, but its hook only prints a message during global installation.
package.jsonView on unpkg · L23Code excerpt · 3 lines
Affected versions and remediation
This report applies to @boxes-dev/dvb@1.0.1029.
See all versions of @boxes-dev/dvb for other recorded verdicts.
- Review the evidence and your use of @boxes-dev/dvb@1.0.1029 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.