nebula-notebook@0.2.51
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 postinstall script does not perform its nested installation behavior when installed as a dependency. Inspected runtime behavior is consistent with a local notebook application, with no concrete malicious chain identified.
Decision evidence
public snapshot- The package defines a postinstall hook, but its installer exits when running from node_modules.
- The command-line launcher starts the bundled server only when the user invokes the package command.
- Resource collection runs fixed GPU diagnostic commands rather than constructed shell input.
- The only identified outbound request is a version check to the npm registry, with an environment-variable opt-out.
- The bundled frontend requires a user click before executing inline notebook-output scripts.
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.51.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.51 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.