nebula-notebook@0.2.54
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 registry-install postinstall path exits before performing its checkout-only commands. Inspected runtime behavior is consistent with a local notebook service and contains no concrete malicious chain.
Decision evidence
public snapshot- The install hook invokes the included postinstall script, which exits when installed under node_modules.
- The command-line launcher starts the packaged local server using the caller's arguments.
- Resource collection uses bounded GPU-status commands with a timeout.
- The frontend constructs authenticated requests from configured request settings.
- Session-token fallback is restricted to non-browser loopback requests.
- The only inspected outbound request checks this package's latest version at the npm registry.
Source & flagged code
10 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.54.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.54 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.