# Paket Maintainer Pulse

> Paket Maintainer Pulse 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-13).

Returns a composite health signal for an open-source package, combining repository vitality metrics from deps.dev (stars, forks, issues, licence, OpenSSF scorecard) and optional GitHub activity data (last push, recent commits).

## Facts

- Endpoint: POST https://paket.halowerk.com/v1/maintainer-pulse
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paket-maintainer-pulse-5c33f197
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_leTDkdOhwjWTS6VxdgjSL

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-maintainer-pulse-5c33f197 -d '<json body>'
```

Example prompt: Can you check the maintainer pulse for the 'express' npm package — I want to know if it's still actively maintained, including its OpenSSF scorecard, star count, open issues, and when it last had commits pushed?

## When to prefer this

Use this endpoint when you need a quick, normalised health signal for a single package combining community vitality (stars, forks, issues) and security posture (OpenSSF scorecard) in one call. It is preferable to scraping GitHub directly because deps.dev data is rate-limit-free and the endpoint gracefully degrades when GitHub is unavailable. Choose this over the version-history or release-cadence endpoints when your primary concern is whether the upstream project is alive and trustworthy, not when it was last released.

## Known failure modes

- Package not found in the specified ecosystem — endpoint returns an error or empty result
- GitHub rate limit exceeded (60 req/hr per IP without auth) — GitHub fields marked unavailable, deps.dev fields still returned
- Invalid or unsupported ecosystem specified — validation error
- Network timeout reaching upstream deps.dev or GitHub APIs — partial or error response
- Malformed request body — 400-level error with details

## How this service works

Answers whether the project behind a package is still alive, from two sources with different roles. deps.dev supplies stars, forks, open issue count, the declared licence and the OpenSSF scorecard without any rate limit or account. GitHub supplies the last push and recent commit activity, but only sixty requests per hour per IP without authentication, so it is treated as optional: when it is unavailable the response still comes back, the affected fields are named as unavailable, and the…

## Output

A JSON response containing repository vitality indicators sourced from deps.dev (star count, fork count, open issue count, declared licence, OpenSSF scorecard score) and, when available, GitHub activity signals (date of last push, recent commit cadence). If GitHub rate limits are hit, the GitHub-sourced fields are marked as unavailable while the deps.dev fields are still returned.

## 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"
  },
  "use_github": {
   "type": "boolean",
   "default": true,
   "description": "Whether to try GitHub for push activity. Off makes the call faster and never rate-limited."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paket-maintainer-pulse-5c33f197/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)