nebula-notebook@0.2.56
AI-native notebook computing environment — real Jupyter kernels, real filesystem, built to be driven by agents (Claude Code / Codex) via MCP
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe install hook is inert for normal node_modules installation, and inspected runtime behavior is consistent with a local notebook service. No concrete malicious behavior was found.
Decision evidence
public snapshot- The lifecycle hook exits when installed under node_modules, so its recursive install code does not run for normal package installation.
- The CLI starts the packaged local server with inherited standard input and output.
- Resource collection uses fixed GPU diagnostic commands.
- Session-token fallback is restricted to loopback, non-browser requests and excludes another operating-system user.
- The browser bundle requests settings through its configured server connection.
- The only fixed external endpoint found is the package's npm registry update check.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage contains a possible secret pattern.
dist/assets/index-C1Zybu-V.jsView on unpkg · L826Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.56.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.56 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.