# dep.halowerk.com Maintainer Concentration Calculator

> dep.halowerk.com Maintainer Concentration Calculator is a paid API for AI agents from dep.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Calculates the ownership share held by the single largest maintainer from a supplied list of maintainers and their weights, returning a concentration metric for dependency health analysis.

## Facts

- Endpoint: POST https://dep.halowerk.com/v1/maintainer-concentration
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dep-halowerk-com-maintainer-concentration-calculator-459ae6e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_THqXCvwNCJJ3TOt1vPxLv

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 dep-halowerk-com-maintainer-concentration-calculator-459ae6e7 -d '<json body>'
```

Example prompt: Calculate the maintainer concentration for this package — the maintainers and their ownership weights are: Alice with 6500, Bob with 2000, Carol with 1500. What share does the top maintainer hold?

## When to prefer this

Use this endpoint when you have explicit numerical ownership or contribution weights for a package's maintainers and need to quantify concentration risk — specifically the share commanded by the single largest stakeholder. It is ideal for supply chain audits, SBOM health scoring, or automated dependency vetting pipelines where bus-factor and single-point-of-failure risk must be measured programmatically. Prefer it over manual heuristics when you have structured weight data from registries or internal measurements.

## Known failure modes

- Empty or missing maintainers array returns validation error
- All weights zero may produce null or undefined concentration
- More than 10,000 maintainer entries rejected due to maxItems limit
- Negative weights rejected by schema minimum constraint
- Missing required 'name' or 'weight' fields on any item causes request failure
- Network timeout on very large maintainer arrays

## How this service works

Measures the share held by the largest maintainer from supplied ownership weights. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age. 

## Output

Returns the fractional share (0–1) held by the single largest maintainer by weight, along with any unavailable fields listed in unavailable_fields, and metadata disclosing whether the value is derived or source-backed (including source, time window, and age where applicable).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "maintainers": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "name",
     "weight"
    ],
    "properties": {
     "name": {
      "type": "string",
      "maxLength": 512,
      "minLength": 1,
      "description": ""
     },
     "weight": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": 0,
      "description": ""
     }
    },
    "additionalProperties": false
   },
   "maxItems": 10000,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dep-halowerk-com-maintainer-concentration-calculator-459ae6e7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dep.halowerk.com](https://www.zero.xyz/host/dep.halowerk.com/llms.txt)