nebula-notebook@0.2.31
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-aiThis is not malicious install-hook abuse: the postinstall script exits for npm installations and there is no self-dependency chain. The package nevertheless exposes high-impact agent, token, and shell capabilities, so it warrants a warning for dangerous capability.
Decision evidence
public snapshot- The running server can create login-shell terminal sessions.
- A protected remote-agent route forwards the caller's session token over SSH and writes it to the user's Nebula token path.
- The package includes agent and terminal control features with filesystem and command execution capability.
- The postinstall hook exits immediately when installed from npm under node_modules.
- There is no runtime dependency on nebula-notebook itself.
- The only identified external request is an opt-outable npm-registry update check; no exfiltration endpoint was found.
- No install-time mutation of AI-agent configuration occurs for npm consumers.
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.31.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.31 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.