lightbase-edge@0.1.4
Superseded — use 0.1.15 (the maintained 0.1.1 line with the framework-prep fix).
The one-liner: full-Node SSR on Cloudflare Pages with ZERO Cloudflare Workers. Drop into any codebase — bundles your server, publishes it to your own Pages CDN, registers a sha-pinned auto-deploy manifest with Lightbase, and generates the preflight-free z
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe package exposes a command-line entrypoint without install lifecycle scripts. The inspected deployment request uses an environment-configured endpoint and caller-supplied credentials; the scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes cli.mjs as a CLI and main entrypoint; it declares no lifecycle scripts.
- cli.mjs takes the command from process.argv and maps named commands to handlers.
- Deployment requires LIGHTBASE_URL, project ID, and a caller-provided token; no URL is hard-coded as the deployment recipient.
- The manifest PUT sends the deployment token to the endpoint constructed from LIGHTBASE_URL.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
cli.mjsView on unpkg · L136cli.mjs takes the command from process.argv and maps named commands to handlers.
cli.mjsView on unpkg · L1680Findings
Affected versions and remediation
This report applies to lightbase-edge@0.1.4.
See all versions of lightbase-edge for other recorded verdicts.
- Review the evidence and your use of lightbase-edge@0.1.4 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.