nebula-notebook@0.2.36
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 install hook is guarded to exit for normal npm installations, while the launcher only invokes the packaged server. The inspected client bundle uses same-origin API calls and no concrete malicious behavior was found.
Decision evidence
public snapshot- The manifest runs a postinstall script.
- The postinstall script exits when installed under node_modules, so the npm install path does not run its nested installs.
- The launcher only starts the bundled local server with user-provided arguments.
- The inspected browser bundle uses relative /api requests for the notebook UI.
- No credential harvesting, external payload download, or unconsented configuration mutation was found in the inspected lifecycle, launcher, or bundle code.
- The only inspected external endpoint is a notify-only npm registry version check at server startup.
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.36.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.36 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.