registry / nebula-notebook / 0.2.80
nebula-notebook@0.2.80
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 18d ago · by lpm-firewall-aiThe lifecycle hook is present, but its source exits for installations under node_modules and limits its installs to checkout subpackages. The inspected runtime indicators serve notebook functionality or check the package’s registry version; none establishes concrete attack behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Package installation, launching the notebook server, or using the server’s resource features.
Impact
No malicious effect was established from these behaviors.
Mechanism
The published-install postinstall exits inside node_modules; the launcher starts the package’s server, and the resource service invokes fixed GPU probes.
AI rationale
The lifecycle hook is present, but its source exits for installations under node_modules and limits its installs to checkout subpackages. The inspected runtime indicators serve notebook functionality or check the package’s registry version; none establishes concrete attack behavior.
Evidence
package.jsonscripts/postinstall.cjsbin/nebula-notebook.jsnode-server/dist/resources/resource-service.jsnode-server/dist/update-check.jsdist/assets/index-pBlQK-xI.jsdist/assets/index-BdZ_Kjti.jsdist/assets/services-shim-zXtxqviK.js
Network endpoints1
registry.npmjs.org/nebula-notebook/latest
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs a postinstall script; that script exits in node_modules and otherwise installs dependencies only for checkout subpackages.
- The launcher starts the package’s own node-server entrypoint and passes through the supplied arguments.
- The resource service runs fixed GPU-information commands with a timeout; it does not build commands from user input.
- The frontend health check requests the same-origin health API.
- The Jupyter bundle’s dynamic require loads a path selected through Jupyter configuration.
- The services shim imports the frontend bundle, and the update checker requests the package’s registry version.
Evidence against
- The flagged shell, dynamic-code, and network patterns have source-supported product contexts; no concrete attack behavior was identified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShellWebSocket
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/assets/index-pBlQK-xI.jsView file
826patternName = generic_password
severity = medium
line = 826
Medium
Secret Pattern
Package contains a possible secret pattern.
dist/assets/index-pBlQK-xI.jsView on unpkg · L826Findings
6 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/nebula-notebook.js
HighShellnode-server/dist/resources/resource-service.js
HighCross File Remote Execution Contextbin/nebula-notebook.js
HighRuntime Package Installscripts/postinstall.cjs
HighSemantic Analysis Limiteddist/assets/index-BdZ_Kjti.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumSecret Patterndist/assets/index-pBlQK-xI.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/assets/index-BdZ_Kjti.js
Affected versions and remediation
This report applies to nebula-notebook@0.2.80.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.80 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.