# Paket Package Freshness Scorer

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

Scores the maintenance health of a software package by analyzing its release cadence and deprecation status, returning a letter grade from A to E.

## Facts

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

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-package-freshness-scorer-f9a893e8 -d '<json body>'
```

Example prompt: Can you score the maintenance freshness of the 'lodash' package? The newest stable release is 180 days old, the median gap between the last ten releases is 60 days, the silence-to-median ratio is 3.0, and the package is not deprecated.

## When to prefer this

Use this endpoint when you need a structured, quantitative maintenance signal for a package and already have (or can compute) the four numeric inputs. It is ideal for CI pipelines, dependency audits, or agent workflows that need a normalized A–E grade rather than raw release data. Prefer sibling endpoints if you need to first fetch the release history or resolve the version timeline before scoring.

## Known failure modes

- Missing required input fields (age, median gap, silence ratio, or deprecation flag) result in a validation error
- Negative or nonsensical numeric inputs (e.g. negative age) may return an error or undefined grade
- If the silence ratio is extremely large due to a division-near-zero scenario, the grade may default to E
- Network or service errors return a non-200 response with an error message

## How this service works

Turns the release history of a package into a maintenance signal an agent can act on. Four measurements go in: the age in days of the newest stable release, the median gap between the last ten releases, the ratio of the current silence to that median, and whether the newest version is deprecated. Each maps to a component score and the components combine into a grade from A to E.

## Output

Returns a structured response containing individual component scores (for release age, median release gap, silence ratio, and deprecation status) plus a combined maintenance grade from A (healthy, active) to E (stale or abandoned), which an agent can use to decide whether to retain, replace, or flag a dependency.

## 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"
  },
  "include_prereleases": {
   "type": "boolean",
   "default": false,
   "description": "Whether pre-releases count as releases for the rhythm. Off by default: a nightly build stream would mask a dormant stable line."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-package-freshness-scorer-f9a893e8/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)