nebula-notebook@0.2.37
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 2mo ago · by lpm-firewall-aiThe concerning lifecycle and child-process primitives are limited to transparent repository setup or launching the bundled server. The registry-install guard prevents the package-manager commands from executing when this package is installed as a dependency.
Decision evidence
public snapshot- The manifest automatically invokes a post-install helper.
- The helper contains package-manager commands, but it exits when installed from node_modules.
- The command-line launcher starts the bundled local server with user-supplied arguments.
- The flagged frontend file is a prebuilt asset map, not an install-time loader.
- No runtime dependency selects another nebula-notebook release.
- The post-install helper does not run its install commands for a registry installation.
- The launcher only starts the package's local server and inherits its process environment.
- No source inspected shows credential collection, data exfiltration, foreign agent configuration writes, or remote payload execution.
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 unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/assets/index-BnQLGXqd.jsView on unpkgFindings
Affected versions and remediation
This report applies to nebula-notebook@0.2.37.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.37 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.