# GitHub Repository Supply-Chain Security & License Auditor

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

Scans a GitHub repository for license risk, maintenance health, popularity signals, and dependency supply-chain vulnerabilities before integrating or executing its code.

## Facts

- Endpoint: GET https://mesh.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: mesh.agentdiet.dev
- Website: https://mesh.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/mesh-agentdiet-dev-github-repository-supply-chain-security-license-66fed36d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l6VGxX_N0_b4HvUw6ABzf

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 mesh-agentdiet-dev-github-repository-supply-chain-security-license-66fed36d
```

Example prompt: Can you audit the langchain-ai/langgraph GitHub repo for me — I want to know its license risk, how actively it's maintained, how popular it is, and whether there are any supply-chain security concerns before I add it as a dependency?

## When to prefer this

Choose this endpoint when an agent or developer needs to programmatically vet a GitHub repository before adopting it as a dependency, running its code, or recommending it — specifically when license risk, supply-chain security, and maintenance health are all needed in a single call. Prefer this over manual GitHub inspection or generic web search when structured, machine-readable security signal is required for automated decision-making in CI pipelines, coding agents, or procurement workflows.

## Known failure modes

- Invalid repo format (not owner/name) returns a validation error
- Private or non-existent repositories return a not-found or access-denied error
- GitHub API rate limiting may cause intermittent failures or degraded data
- Repositories with no declared license return ambiguous license risk results
- Very new repos with minimal history may yield incomplete maintenance velocity signals

## 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://mesh.agentdiet.dev/v1/repo-supply-chain-scan)

## Output

Returns a structured security report for the specified GitHub repository including: license type and commercial-use risk level, maintenance velocity indicators (commit frequency, last activity), community signals (stars, forks), 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/mesh-agentdiet-dev-github-repository-supply-chain-security-license-66fed36d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mesh.agentdiet.dev](https://www.zero.xyz/host/mesh.agentdiet.dev/llms.txt)