# GitHub Repository License, Dependency & Supply-Chain Security Auditor

> GitHub Repository License, Dependency & Supply-Chain Security Auditor is a paid API for AI agents from onchain-risk.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-23).

Evaluates a GitHub repository for license risk, maintenance velocity, stars/forks, and supply-chain security before code execution or dependency adoption.

## Facts

- Endpoint: POST https://onchain-risk.agentdiet.dev/v1/license-compliance-scan?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Provider: onchain-risk.agentdiet.dev
- Website: https://onchain-risk.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/onchain-risk-agentdiet-dev-github-repository-license-dependency-d03cf692
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nh-NrtCGw922MFbGX68uT

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 onchain-risk-agentdiet-dev-github-repository-license-dependency-d03cf692 -d '<json body>'
```

Example prompt: Before we add langchain-ai/langgraph as a dependency, can you run a full license compliance and supply-chain security audit on it so I know if there are any GPL conflicts or maintenance red flags?

## When to prefer this

Use this endpoint when an AI coding agent needs to vet a GitHub repository before adding it as a dependency, executing its code, or recommending it to a user — especially in enterprise or compliance-sensitive contexts where license type (MIT vs GPL vs proprietary), supply-chain integrity, and maintenance health all matter. Prefer this over generic GitHub API calls when you need a consolidated risk score rather than raw metadata.

## Known failure modes

- Invalid or non-existent repo format (e.g. missing owner/name) returns a validation error
- Private or inaccessible repositories may return an authorization or not-found error
- GitHub API rate limits could cause transient failures or incomplete results
- Repos with no license file may return an undetermined license risk classification
- Network timeouts on large repos with many dependencies

## 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://onchain-risk.agentdiet.dev/v1/license-compliance-scan)

## Output

A structured report covering the repository's detected license type and its risk level (permissive vs. copyleft vs. restrictive), maintenance velocity indicators (commit frequency, last activity), community signals (stars, forks), and supply-chain security findings such as vulnerable or suspicious dependencies — giving the agent a go/no-go signal before adopting or executing the code.

## 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/onchain-risk-agentdiet-dev-github-repository-license-dependency-d03cf692/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onchain-risk.agentdiet.dev](https://www.zero.xyz/host/onchain-risk.agentdiet.dev/llms.txt)