nebula-notebook@0.2.55
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 1mo ago · by lpm-firewall-aiThe lifecycle hook is explicitly inactive when installed as a dependency, and the inspected runtime behavior is consistent with a local notebook service. No concrete attack behavior was found.
Decision evidence
public snapshot- Package metadata defines the published command and its postinstall hook; it has no runtime dependency on its own package name.
- The command starts the packaged local server with the caller's arguments and environment.
- The postinstall script exits when running under node_modules, so registry installation does not run its nested npm installs.
- Resource collection only invokes fixed GPU-information commands with a timeout.
- The bundled client uses Jupyter-style request authentication handling; no package-controlled exfiltration endpoint was found in the inspected paths.
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-D7GWSc_e.jsView on unpkg · L826Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.55.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.55 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.