nebula-notebook@0.2.27
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-aiStatic inspection shows the suspicious postinstall path is explicitly disabled when installed from npm. Remaining execution and package-install primitives are runtime notebook/kernel functionality and no concrete malicious chain was found.
Decision evidence
public snapshot- postinstall invokes npm only for repo-checkout subpackages.
- Runtime can install ipykernel for a user-selected writable Python environment.
- Published npm installs exit from postinstall before any command runs.
- CLI only launches the packaged local server with user-supplied flags.
- No credential harvesting, covert exfiltration, remote payload loading, or foreign AI-agent config mutation found.
- The sole fixed network endpoint is an npm registry version check.
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-CuNblSZD.jsView on unpkgFindings
Affected versions and remediation
This report applies to nebula-notebook@0.2.27.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.27 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.