nebula-notebook@0.2.83
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 15d ago · by lpm-firewall-aiThe scanner's lifecycle, child-process, and dynamic-code flags resolve to a checkout-only setup hook, a launcher for the bundled server, bounded local GPU queries, and a Jupyter configuration loader. The inspected source supports normal package functionality, with no concrete attack behavior identified.
Decision evidence
public snapshot- The manifest's postinstall invokes scripts/postinstall.cjs; that script exits when its directory is under node_modules, and otherwise installs the checkout's subpackages.
- The launcher starts the bundled server and forwards its arguments and environment; the server starts a local Fastify service.
- The resource service runs local GPU information commands with a timeout; its commands query nvidia-smi and rocm-smi.
- The reviewed bundles and flagged runtime files correspond to UI loading, authentication, Python discovery, notebook undo/redo, scheduler setup, remote-agent identity, and Fastify plugins.
- The three inspected dependency manifests and entrypoints identify Fastify CORS, multipart, and static-file plugins.
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-pBlQK-xI.jsView on unpkg · L826Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.83.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.83 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.