@boxes-dev/dvb@1.0.1053
The boxes.dev CLI: run Claude Code and Codex on cloud devboxes from your terminal
AI security review
scanned · by lpm-firewall-aiThe lifecycle hook performs no configuration mutation or payload execution. Network, process, environment, and file operations support user-invoked runtime management; the wildcard dependency names a separate runtime package rather than a lifecycle self-dependency.
Decision evidence
public snapshot- package.json runs scripts/postinstall.cjs; that hook only prints a global-install setup hint.
- The CLI retrieves updates for the separate @boxes-dev/dvb-runtime package from the npm registry.
- User invocation stages the runtime and starts the package updater; dvbd uses the same launcher.
- Standalone updates use deploy.boxes.dev and verify the archive SHA256 before execution.
- The background updater shuts down when its recorded installation owner disappears.
- deploy.boxes.dev
- registry.npmjs.org
Findings
1 high · 5 medium · 6 lowAutomated scan signals; the review checked them and cleared this version. Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
package.json1 high · 1 medium · 1 lowShow all 12 findings
package.json3 findingsSource & flagged code
3 flaggedThe lines the automated scan flagged. The review checked them and cleared this version.
Package 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 runs scripts/postinstall.cjs; that hook only prints a global-install setup hint.
package.jsonView on unpkg · L35Code excerpt · 2 lines
Versions and review status
This report applies to @boxes-dev/dvb@1.0.1053.
See all versions of @boxes-dev/dvb for other recorded verdicts.
- No action is needed for @boxes-dev/dvb@1.0.1053. Pin the version in your lockfile and check new releases as they are scanned.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.