nebula-notebook@0.2.13
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 normal npm dependency installation, while observed shell, filesystem, kernel, and agent features are activated through the notebook service. No concrete malicious chain was found by source inspection.
Decision evidence
public snapshot- scripts/postinstall.cjs exits when installed under node_modules, so published dependency installs do not run nested npm installs.
- bin/nebula-notebook.js only launches the bundled local server after explicit CLI invocation.
- node-server/dist/update-check.js only fetches the package's npm-registry latest-version endpoint; it does not install or execute updates.
- Agent state/config writes are package-owned .nebula files, not foreign AI-agent configuration.
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 unpkgPackage contains a possible secret pattern.
dist/assets/index-NfxQwPBq.jsView on unpkg · L791Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.13.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.13 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.