nebula-notebook@0.2.24
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-aiStatic inspection found a feature-rich notebook server, but its risky primitives are package-aligned and runtime/user-invoked. The postinstall hook explicitly exits for normal node_modules installs, and no concrete malicious chain was found.
Decision evidence
public snapshot- Defines a postinstall lifecycle hook.
- Postinstall can invoke npm install in checkout subdirectories.
- Runtime performs a package-version update check.
- Postinstall exits when installed under node_modules, so published dependency installs do not run its npm commands.
- The update request targets only nebula-notebook metadata and is documented as notify-only.
- No source evidence of credential exfiltration, remote payload loading, or foreign AI-agent configuration mutation.
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 unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/assets/index-CuNblSZD.jsView on unpkgFindings
Affected versions and remediation
This report applies to nebula-notebook@0.2.24.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.24 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.