lightbase-edge@0.1.1
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 27d ago · by lpm-firewall-aiSource inspection found no install-time hook or independent attack behavior. Network use and the optional postbuild hook are part of the user-invoked deployment workflow and use caller-configured settings.
Decision evidence
public snapshot- The manifest defines a CLI entry point and dependency, with no install lifecycle hook.
- The repository metadata points to the Lightbase repository and the package subdirectory.
- Deployment requires caller-provided Lightbase URL, project ID, and token.
- The deploy command bundles the configured server and registers it with the configured Lightbase endpoint.
- Init adds a postbuild deploy hook only when the user runs the init command.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
cli.mjsView on unpkg · L134Deployment requires caller-provided Lightbase URL, project ID, and token.
cli.mjsView on unpkg · L61Findings
Affected versions and remediation
This report applies to lightbase-edge@0.1.1.
See all versions of lightbase-edge for other recorded verdicts.
- Review the evidence and your use of lightbase-edge@0.1.1 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.