# GitHub Repo Dependency & License Security Auditor

> GitHub Repo Dependency & License Security Auditor is a paid API for AI agents from json-repair.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-21).

Audits a GitHub repository for license risk, maintenance health, stars/forks metrics, and supply-chain security vulnerabilities before integrating or executing code.

## Facts

- Endpoint: GET https://json-repair.agentdiet.dev/v1/repo-supply-chain-scan?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: json-repair.agentdiet.dev
- Website: https://json-repair.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/json-repair-agentdiet-dev-github-repo-dependency-license-security-d0f41772
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KPYt9TFr8iQMh-EjBd4_s

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 json-repair-agentdiet-dev-github-repo-dependency-license-security-d0f41772
```

Example prompt: Before I add langchain-ai/langgraph as a dependency in my project, can you audit its GitHub repo for license risks, how actively it's maintained, and any supply-chain security issues?

## When to prefer this

Choose this endpoint when a coding agent or developer needs to vet an open source GitHub repository before adoption — specifically to check license compliance, assess maintenance health, gauge community traction, or identify supply-chain risks. It is ideal as a pre-flight check before adding a new dependency, auditing a vendor's codebase, or evaluating third-party libraries for production use. Prefer it over generic web search when structured, machine-readable security and compliance metadata about a specific repo is required.

## Known failure modes

- Invalid or non-existent repo format returns an error (e.g. malformed owner/name)
- Private repositories inaccessible to GitHub's public API return a not-found or forbidden response
- GitHub API rate limiting may cause transient failures
- Repos with no package manifests may return limited dependency data
- Network timeouts if GitHub is slow to respond

## How this service works

Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and supply-chain security before code execution. (Live x402 v2, IETF MPP & MCP endpoint at https://json-repair.agentdiet.dev/v1/repo-supply-chain-scan)

## Output

Returns a structured report covering the repository's detected license type and associated risk level, maintenance velocity indicators (commit frequency, last commit date), popularity signals (stars and forks counts), and supply-chain security findings such as dependency vulnerabilities or suspicious package patterns.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "repo"
 ],
 "properties": {
  "repo": {
   "type": "string",
   "minLength": 1,
   "description": "GitHub repository in owner/name format (e.g. modelcontextprotocol/servers or langchain-ai/langgraph)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/json-repair-agentdiet-dev-github-repo-dependency-license-security-d0f41772/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from json-repair.agentdiet.dev](https://www.zero.xyz/host/json-repair.agentdiet.dev/llms.txt)