Docs / More / FAQ

FAQ

Does kedgeway send my code anywhere?

No. It sends one fixed script to Stellar Raven, with nothing from your repo in it. The comparison happens on your machine.

Why do I have to log in?

Live ecosystem data comes from the Stellar Raven MCP server, which requires OAuth. You log in once; the token is stored at ~/.config/kedgeway/auth.json.

Does it change my repo?

diagnose never does. kedgeway migrate is a dry run unless you pass --write, and it refuses to write over uncommitted git changes.

Can I log in on a server without a browser?

Yes. kedgeway login --no-browser prints the URL; sign in anywhere and paste the redirect URL or code back, or forward the callback port with ssh -L. See Authentication.

Can I run it offline?

Yes. --offline reuses the cached Raven snapshot from your last live run, and --fixture uses a snapshot file. See Data sources and Fixtures.

Why do I get SDK_UNKNOWN?

Either the version in your manifest cannot be read as a single major (for example an upper bound or a compound range), or the current major was unavailable. See What it scans and DATA_DEGRADED.

Does it read my lockfile?

Yes, when one is present. Cargo.lock, package-lock.json, pnpm-lock.yaml and yarn.lock supply the resolved version of each direct dependency, and that version is what the comparison uses. If the lockfile is missing or ambiguous, kedgeway falls back to the manifest and says so. See What it scans.

Which --fail-on should I use in CI?

critical fails on deprecated SDKs and legacy packages. warning also fails on one-major-behind and unknowns. See CI.

Is it on npm?

Yes. npm install -g kedgeway. It needs Node 22.12 or newer.