# Paket Dependency Bloat Scorer

> Paket Dependency Bloat Scorer is a paid API for AI agents from paket.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Scores the cost of depending on a package by analyzing its resolved transitive graph across four metrics—node count, max depth, multi-version conflicts, and root fan-out—returning a grade from A to E with full threshold details.

## Facts

- Endpoint: POST https://paket.halowerk.com/v1/dependency-bloat
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paket-dependency-bloat-scorer-fb49dbcb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gt05_cUmoBQWY0PlyWDXx

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability paket-dependency-bloat-scorer-fb49dbcb -d '<json body>'
```

Example prompt: Can you score the dependency bloat for the npm package 'express' at version 4.18.2 and tell me what grade it gets, along with the transitive node count, max depth, version conflicts, and root fan-out?

## When to prefer this

Choose this endpoint when you need an objective, graph-resolved measurement of dependency weight rather than a simple direct-dependency count or heuristic guess. It is especially valuable before adopting a new library, enforcing bloat budgets in CI pipelines, or comparing candidates, because the grade and thresholds are returned together enabling custom re-weighting without re-calling the API.

## Known failure modes

- Unknown package or version returns a 404 with no graph available
- Unsupported ecosystem returns a 400 validation error
- Ambiguous package name across ecosystems may require explicit ecosystem qualifier
- Graph resolution timeout for very large transitive trees
- Stale registry data may cause inaccurate node counts for recently published packages

## How this service works

Scores how much a package costs to depend on, using the resolved graph rather than a guess. Four measurements: the number of transitive nodes, the maximum depth, how many packages appear at more than one version, and the fan-out of the root. From those comes a grade from A to E with every threshold returned, so the judgement can be recomputed with different weights.

## Output

Returns four numeric measurements (transitive node count, maximum graph depth, number of packages appearing at more than one version, and root fan-out), a letter grade from A to E summarizing overall bloat, and the full set of thresholds used to compute the grade so it can be recalculated with custom weights.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 300,
   "minLength": 1
  },
  "system": {
   "enum": [
    "npm",
    "pypi",
    "maven",
    "go",
    "cargo",
    "nuget",
    "rubygems"
   ],
   "type": "string"
  },
  "version": {
   "type": "string",
   "maxLength": 60
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-dependency-bloat-scorer-fb49dbcb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from paket.halowerk.com](https://www.zero.xyz/host/paket.halowerk.com/llms.txt)