nebula-notebook@0.2.85
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 13d ago · by lpm-firewall-aiNo malicious behavior was identified in the inspected source. The flagged patterns correspond to guarded repository setup and expected notebook functions, with no unresolved attack path established.
Decision evidence
public snapshot- The manifest defines a postinstall hook, but the hook exits when installed under node_modules; outside that path, it performs setup only for existing project subdirectories.
- The launcher starts the package's bundled server, which listens on its configured host and port.
- Shell use is tied to fixed GPU information queries with timeouts; environment discovery runs commands through its feature-specific runner.
- Inspected authentication, notebook, setup-prompt, and remote-identity code supports local product functions; no unrelated account or credential transfer was identified.
- The browser bundle uses relative API routes for authenticated requests; its dynamic require loads configured Jupyter settings.
- The inspected Fastify dependency snapshots implement CORS, multipart handling, and static-file serving. Their manifests show ordinary package metadata and no install lifecycle hooks.
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 unpkgPackage contains a possible secret pattern.
dist/assets/index-pBlQK-xI.jsView on unpkg · L826Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.85.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.85 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.