nebula-notebook@0.2.47
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 inert for registry consumers, but the runtime remote-agent flow writes an authentication token through SSH. That is a real, user-invoked agent capability with no evidence of covert exfiltration or install-time compromise.
Decision evidence
public snapshot- The package declares a postinstall hook whose checkout-only branch runs npm install.
- A runtime API forwards the caller's bearer token over SSH and writes it to a remote .nebula/token file.
- The postinstall script exits when installed under node_modules, so the registry install path does not run its nested npm installs.
- The SSH token operation validates port, username, and token shape and is invoked by a remote-agent API rather than automatically at installation.
- No source evidence showed secret exfiltration, remote payload download, or mutation of third-party AI-agent configuration.
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-D7GWSc_e.jsView on unpkg · L826Findings
Affected versions and remediation
This report applies to nebula-notebook@0.2.47.
See all versions of nebula-notebook for other recorded verdicts.
- Review the evidence and your use of nebula-notebook@0.2.47 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.