Extract Dependencies

code.extract_dependencies

ProductionBounded custom (Class B)Deterministicverifiablefastv1.0.0

No network

Overview

When you supply manifest or lockfile contents, we parse them into a normalized dependency inventory with manager, scope, and version spec. JSON and XML manifests have high fidelity; some formats use bounded heuristics. We do not install packages, run builds, or resolve transitive graphs against a registry — do not use this when you need authoritative resolution or vulnerability data.

You need a dependency inventory without running installs or builds. We parse what you send and return a stable, sorted list.

Reliability

Deterministic extraction with stable ordering. High fidelity for JSON/XML manifests; heuristic formats may emit warnings instead of failing. Invalid file shapes throw validation errors — fix the input before retrying.

Context footprint

Returns detected ecosystems, a sorted dependency list, and warnings. A successful call costs 1 execution credit.

When to use it

When you have manifest text and need a normalized dependency list.

When full transitive resolution against a registry is required.

Scope

Note

Extracts a normalized dependency list from manifests you supply.

Non-goals

Does not install packages
Does not run build tools
Does not query vulnerability data
Does not resolve version ranges against a registry
Heuristic parsers may miss exotic TOML or Gradle syntax

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysisparsing

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input2 MB

How we handle your data

Sensitive input, safe output

What this means

This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response does not contain submitted content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
files	array	Yes	From 0 through 200 closed dependency-manifest files, each with a filename that selects the parser and the exact text.
ecosystemHint	string	No	Inert ecosystem hint; omit it because filenames select parsers.
includeDevDependencies	boolean	No	Whether development scopes are included; omit it for true.
includeTransitiveFromLockfile	boolean	No	Inert lockfile flag; omit it because every lockfile package is included.

Output schema

Field	Type	Required	Description
ecosystems	array	Yes	From 0 through 9 recognized ecosystem names such as npm or maven, in first-seen order.
dependencies	array	Yes	From 0 through 100,000 normalized dependencies in stable order.
warnings	array	Yes	From 0 through 200 parser warnings, at most one per supplied file.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"code.extract_dependencies","input":{"files":[{"filename":"package.json","content":"{}"}]}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("code.extract_dependencies", {"files":[{"filename":"package.json","content":"{\"dependencies\":{\"react\":\"^18.0.0\"}}"}]});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not install packages
Does not run build tools
Does not query vulnerability data
Does not resolve version ranges against a registry
Heuristic parsers may miss exotic TOML or Gradle syntax
Registry-backed transitive resolution
Software composition analysis with CVE data

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "code.extract_dependencies",
  "input": {
    "files": [
      {
        "filename": "package.json",
        "content": "{\"dependencies\":{\"react\":\"^18.0.0\"}}"
      }
    ]
  }
}

Examples

npm package.json runtime dependency

Inputjson

{
  "files": [
    {
      "filename": "package.json",
      "content": "{\"dependencies\":{\"react\":\"^18.0.0\"}}"
    }
  ]
}

Expected outputjson

{
  "ecosystems": [
    "npm"
  ],
  "warnings": [],
  "dependencies": [
    {
      "versionSpec": "^18.0.0",
      "sourceFile": "package.json",
      "name": "react",
      "scope": "runtime",
      "manager": "npm"
    }
  ]
}

Empty manifest yields no dependencies