nebula-notebook@0.2.30
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 2mo ago · by lpm-firewall-aiThe install hook is explicitly disabled for npm dependency installs, while the flagged process and file operations are runtime features of the notebook application. Source inspection found no concrete malicious chain.
Decision evidence
public snapshot- The manifest defines a postinstall hook.
- The runtime server can create user-facing terminal sessions and manage notebook files.
- The postinstall script exits when installed under node_modules, so published dependency installation does not run its nested npm installs.
- The command-line launcher only starts the bundled local server and forwards user-supplied arguments.
- The only fixed outbound endpoint found is the npm registry version check; it reads a version and logs an update notice.
- No credential harvesting, external payload download, obfuscated loader, or foreign AI-agent configuration mutation was found.
Source & flagged code
9 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-DbRuvtfE.jsView on unpkg · L816Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.30.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.30 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.