registry / lightbase-edge / 0.1.16

lightbase-edge@0.1.16

The Lightbase Edge deploy tool: full-Node SSR for any Node codebase (Astro, Nuxt, Next, custom servers) served through the Lightbase edge gateway with a static CDN front. Zero edge functions, zero provisioning, zero rewrites — bundles your server, publish

AI Security Review

scanned 3h ago · by lpm-firewall-ai

The CLI is also the package main entry, and importing it can default to deployment, which may publish artifacts and update a manifest without an explicit deploy command. The destination is configured by the user and fits the package's purpose, so this is a warning-level capability risk rather than a demonstrated attack.

Static reason

One or more suspicious static signals were detected.

Trigger

Import cli.mjs without a command argument; the top-level CLI dispatch defaults to deploy.

Impact

An import may unexpectedly publish project artifacts or change the registered deployment. The service URL is configurable, and no unrelated destination was identified.

Mechanism

The deploy path builds and assembles the project, then can PUT its manifest with the configured deploy token to the configured Lightbase URL.

AI rationale

Evidence

package.jsoncli.mjs${staticOut}/${staticOut}/_lb/${staticOut}/_lb-manifest.json

Network endpoints1

${LIGHTBASE_URL or LIGHTBASE_BASE_URL}/api/v1/projects/${projectId}/edge/apps/${appId}/manifest

Decision evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

The package exposes cli.mjs as both its executable and main entry, so importing the main entry evaluates the CLI.
With no command argument, the CLI defaults to deploy and immediately dispatches that command at top level.
Deploy registration sends the deploy token in an apikey header to the URL selected by LIGHTBASE_URL or LIGHTBASE_BASE_URL.

Evidence against

The package describes itself as a deploy tool, and deploy is an intended command when the executable is run.
The registration URL is supplied through the user's environment; the inspected request does not show a hard-coded unrelated collector.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 111 KB of source, external domains: www.w3.org

Source & flagged code

6 flagged

cli.mjsView file

146package = lightbase-edge; repositoryIdentity = lightbase; dependency = esbuild L146: // (monorepo symlink — npm installs a REAL symlink, not a copy), ESM L147: // import('esbuild') resolves from the package's REAL path, where the host L148: // project's esbuild is invisible → "esbuild is required" on every deploy.

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

cli.mjsView on unpkg · L146

2108const cmd = process.argv[2] || 'deploy'; // BismiLLAH (0.1.6 — always-produce CI): `deploy`/`optimize` NEVER exit early — // without complete credentials they assemble the Pages output and skip only // the manifest PUT, so a CI "output directory" always exists and the live // manifest keeps serving (pinned-bundle preservation keeps the old origin // fetc

Medium

Ai Review Evidence

With no command argument, the CLI defaults to deploy and immediately dispatches that command at top level.

cli.mjsView on unpkg · L2108

1430const resp = await fetch(`${url}/api/v1/projects/${projectId}/edge/apps/${cfg.appId}/manifest`, { method: 'PUT', headers: { "content-type": "application/json", apikey: token, 'x-lightbase-project': projectId, }

Findings

1 High8 Medium3 Low

HighCopied Package Dependency Bridgecli.mjs

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

MediumAi Review Evidencepackage.json

MediumAi Review Evidencecli.mjs

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to lightbase-edge@0.1.16.

See all versions of lightbase-edge for other recorded verdicts.

Review the evidence and your use of lightbase-edge@0.1.16 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: 2026-11-04 22:13:14.896Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / lightbase-edge / 0.1.16

lightbase-edge@0.1.16

AI Security Review

scanned 3h ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.

Trigger

Import cli.mjs without a command argument; the top-level CLI dispatch defaults to deploy.

Impact

An import may unexpectedly publish project artifacts or change the registered deployment. The service URL is configurable, and no unrelated destination was identified.

Mechanism

The deploy path builds and assembles the project, then can PUT its manifest with the configured deploy token to the configured Lightbase URL.

AI rationale

Evidence

package.jsoncli.mjs${staticOut}/${staticOut}/_lb/${staticOut}/_lb-manifest.json

Network endpoints1

${LIGHTBASE_URL or LIGHTBASE_BASE_URL}/api/v1/projects/${projectId}/edge/apps/${appId}/manifest

Decision evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

The package exposes cli.mjs as both its executable and main entry, so importing the main entry evaluates the CLI.
With no command argument, the CLI defaults to deploy and immediately dispatches that command at top level.
Deploy registration sends the deploy token in an apikey header to the URL selected by LIGHTBASE_URL or LIGHTBASE_BASE_URL.

Evidence against

The package describes itself as a deploy tool, and deploy is an intended command when the executable is run.
The registration URL is supplied through the user's environment; the inspected request does not show a hard-coded unrelated collector.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 111 KB of source, external domains: www.w3.org

Source & flagged code

6 flagged

cli.mjsView file

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

cli.mjsView on unpkg · L146

Medium

Ai Review Evidence

With no command argument, the CLI defaults to deploy and immediately dispatches that command at top level.

cli.mjsView on unpkg · L2108

Findings

1 High8 Medium3 Low

HighCopied Package Dependency Bridgecli.mjs

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

MediumAi Review Evidencepackage.json

MediumAi Review Evidencecli.mjs

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to lightbase-edge@0.1.16.

See all versions of lightbase-edge for other recorded verdicts.

Review the evidence and your use of lightbase-edge@0.1.16 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: 2026-11-04 22:13:14.896Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.