Track dependency health over time instead of running one-off scans.

Depsly App turns the public CLI into a repeatable workflow: upload lockfiles, store scan history, compare changes, and review prioritized dependency actions without losing context between runs.

Primary value

Persistent scan history

Core output

Prioritized dependency actions

Operator flow

Upload, compare, decide

Quick scan

Upload `package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`

Running in local anonymous mode. Set NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY to enable sign-in.

Checking session...

Why use the app

Keep the CLI public and local. Use the app when workflow and persistence matter.

Hosted workflow over the CLI

Run Depsly through a hosted product surface that keeps scan history, report delivery, and follow-up analysis in one place.

Designed for repeated review

Compare new lockfiles against prior scans so dependency shape changes become part of an ongoing review process instead of one-off terminal output.

Built for decision-making

Focus on which packages matter, why they matter, and what action is worth taking next instead of treating every dependency equally.

Workflow

Move from upload to action without rebuilding the same analysis every week.

Step 1

Upload a lockfile

Start with a real package-lock.json, yarn.lock, or pnpm-lock.yaml from a JavaScript or TypeScript project.

Step 2

Run the Depsly engine

The backend executes the public CLI and stores structured scan results for later comparison.

Step 3

Review and follow through

Inspect top actions, hotspots, and scenarios without rebuilding context every time.

Product boundary

The public CLI stays useful on its own. The paid product owns hosted workflow.

Depsly App is where scan persistence, report delivery, history, and repeated operator flow belong. That keeps the CLI focused, trustworthy, and easy to adopt while the hosted product solves the workflow layer.