@boxes-dev/dvb@1.0.1014
AI security review
scanned · by lpm-firewall-aiThe inspected lifecycle hook performs no mutation, and the executable behavior matches a runtime launcher and updater. No concrete exfiltration, malicious persistence, or unconsented agent control-surface mutation was established.
Decision evidence
public snapshot- package.json depends on a separate runtime package, not on another release of itself.
- The postinstall hook only prints setup guidance during global installation.
- Runtime updates use the npm registry metadata for @boxes-dev/dvb-runtime.
- The CLI stages its runtime and starts a package updater when invoked; dvbd uses the same launcher.
- Runtime releases use package-owned directories, and standalone downloads receive a SHA256 check.
- The CLI automatically downloads and executes updated runtime code; downloaded releases and dependency contents are outside this snapshot.
- 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 depends on a separate runtime package, not on another release of itself.
package.jsonView on unpkg · L32Code excerpt · 5 lines
Versions and review status
This report applies to @boxes-dev/dvb@1.0.1014.
See all versions of @boxes-dev/dvb for other recorded verdicts.
- No action is needed for @boxes-dev/dvb@1.0.1014. 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.