nebula-notebook@0.2.35
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 only automatic lifecycle behavior is explicitly guarded to exit from node_modules, while the launcher passes user arguments to the bundled server. The inspected high-risk paths show ordinary package functionality rather than a concrete malicious chain.
Decision evidence
public snapshot- The manifest exposes a command-line launcher and runs a postinstall script.
- The postinstall script exits when installed under node_modules, so registry installation does not run its nested npm commands.
- The launcher only starts the bundled local server with the user's arguments and environment.
- The cited frontend artifact is a Vite dependency-map bundle, not an opaque payload.
- The source-checkout postinstall can run npm install in first-party subdirectories.
- The running server performs a daily version check against the npm registry.
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 unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/assets/index-BnQLGXqd.jsView on unpkgFindings
Affected versions and remediation
This report applies to nebula-notebook@0.2.35.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.35 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.