nebula-notebook@0.2.18
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 3mo ago · by lpm-firewall-aiThe install hook is explicitly inert for npm dependency installs, and the flagged execution/network primitives implement the advertised user-launched notebook service. Source inspection found no concrete malicious behavior.
Decision evidence
public snapshot- postinstall exits when installed under node_modules, so published npm installs do not run its nested npm commands.
- CLI only starts the bundled local server after an explicit user invocation.
- Runtime file, terminal, and Python-kernel actions are notebook features invoked through its server routes.
- The sole fixed outbound endpoint is a notify-only npm update check; no credential harvesting or exfiltration was found.
- No package code writes foreign AI-agent configuration paths; .nebula files are package-owned state.
Source & flagged code
8 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/assets/index-Cq1BG1_T.jsView on unpkgFindings
Affected versions and remediation
This report applies to nebula-notebook@0.2.18.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.18 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.