Know before your agent installs.

Dependency Preflight evaluates exact npm and PyPI package versions before installation and returns a structured ALLOW, REVIEW, or BLOCK decision with findings and source evidence.

Open API docs →View free demo View Agentic Market listing

POST /v1/dependency-preflight

{
  "ecosystem": "npm",
  "packages": [
    {
      "name": "example-package",
      "version": "1.0.0"
    }
  ],
  "policy": "balanced"
}

What it does

A machine-readable checkpoint before installation.

Give autonomous coding workflows a compact decision point before they add a dependency.

Request

Submit one or more exact package versions from npm or PyPI.

Evaluate

The service checks metadata and evidence such as known-vulnerability, lifecycle, install-script, release-age, and license-related inputs.

Decide

Receive ALLOW, REVIEW, or BLOCK so the workflow can continue, escalate, or stop.

Capabilities

Built for automation.

Evaluate up to ten exact package versions per request
npm and PyPI ecosystems
Package-level and request-level decisions
Findings plus source evidence in JSON
Pay per use, no subscription required

Technical proof

Inspect the live interfaces.

The public API surfaces are the authoritative service contract.

OpenAPI JSON Service health

Good fits

Package-install decisions with an exact version in hand.

Before changing a lockfile

Evaluate the exact npm or PyPI version an agent wants to introduce before installation.

Bounded batch review

Check up to ten exact versions from one ecosystem in a single request.

Human-review handoff

Use findings and source evidence to support the pause-and-review step when the result is REVIEW.

Important: Dependency Preflight provides informational automation inputs, not a security guarantee or legal opinion. Integrators should rely on the current API documentation and OpenAPI specification for authoritative behavior.