# GitHub Repository Security & License Auditor

> GitHub Repository Security & License 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 velocity, stars/forks, dependency health, and supply-chain security signals before code integration.

## Facts

- Endpoint: GET https://json-repair.agentdiet.dev/v1/repo-audit?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-repository-security-license-auditor-0104a414
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_71g5T9dm0qno3VsvdF-66

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-repository-security-license-auditor-0104a414
```

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

## When to prefer this

Choose this endpoint when an AI coding agent or developer needs to evaluate a GitHub repository before integrating it as a dependency — especially when license compliance, supply-chain security, or maintenance health are concerns. Prefer this over manual GitHub inspection when automating dependency vetting pipelines or when an agent needs structured, machine-readable risk signals. Best suited for pre-integration due diligence rather than ongoing monitoring.

## Known failure modes

- Invalid or non-existent repo name returns an error (e.g. repo not found on GitHub)
- Private repositories may return access-denied or incomplete data
- Rate limiting by upstream GitHub API may cause partial or delayed results
- Repos with no license file may return ambiguous license risk data
- Payment not completed via x402 results in HTTP 402 response blocking the audit

## 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-audit)

## Output

Returns a structured report including the repository's license type and risk level, maintenance velocity (commit frequency, last activity), community signals (stars, forks), dependency security findings, and supply-chain risk indicators to help a developer or agent decide whether to safely integrate the library.

## 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-repository-security-license-auditor-0104a414/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)