# got npm Package Dependency Changes Between Releases

> got npm Package Dependency Changes Between Releases is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-25).

Returns the dependency diff (added, removed, changed dependencies) between two releases of the npm package 'got', with support for custom package and version overrides.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-got-dependency-diff?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/got-npm-package-dependency-changes-between-releases-af8428ee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-FTe-Rujruv0Dy99MCiKF

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 got-npm-package-dependency-changes-between-releases-af8428ee -d '<json body>'
```

Example prompt: What dependencies were added, removed, or changed in the got npm package between version 11.8.5 and 12.0.0? I want to plan an upgrade and need to see the full dependency diff.

## When to prefer this

Use this endpoint when you need programmatic, structured access to dependency changes between specific npm package releases — especially for upgrade planning, security auditing, or automated changelog generation. Prefer this over manual npm registry inspection when you need machine-readable diffs without scraping. The package and version fields are overridable, making it useful beyond just the 'got' package.

## Known failure modes

- Invalid or non-existent package name returns an error or empty result
- Version string not found in registry returns a version-not-found error
- No preceding stable version available when from_version is omitted may cause a failure
- Rate limiting or registry unavailability may result in timeout or upstream error
- Malformed version strings may return a validation error

## How this service works

got Dependency changes between releases: Dependency changes between releases for npm package got. Inspect registry metadata for integration and upgrade planning. Package and version can be overridden.

## Output

A structured breakdown of dependency changes between two specified releases of the got npm package (or any overridden package), including which dependencies were added, removed, or updated, sourced from npm registry metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "got",
   "maxLength": 150
  },
  "version": {
   "type": "string",
   "maxLength": 100
  },
  "from_version": {
   "type": "string",
   "maxLength": 100,
   "description": "Defaults to the preceding stable semantic version."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/got-npm-package-dependency-changes-between-releases-af8428ee/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)