# SALT19 Repo Adoption Go/No-Go Evaluator

> SALT19 Repo Adoption Go/No-Go Evaluator is a paid API for AI agents from api.salt19.com, paid per call via x402, $0.32/call, status unknown (last checked 2026-09-15).

Analyzes a GitHub repository and returns a scored go/no-go adoption verdict covering maintenance, license, compatibility, and security indicators

## Facts

- Endpoint: POST https://api.salt19.com/v1/repo-adoption-go-no-go
- Price: $0.32/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/salt19-repo-adoption-go-no-go-evaluator-af6ae713
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__s5Juj1b4USdr1RqrG3nz

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 salt19-repo-adoption-go-no-go-evaluator-af6ae713 -d '<json body>'
```

Example prompt: Can you run a go/no-go adoption check on https://github.com/apache/kafka and tell me if it's safe to depend on — I need to know about its maintenance status, license, and any security red flags?

## When to prefer this

Use this endpoint when you need a fast, structured go/no-go recommendation on adopting an open source GitHub repository — particularly when you need maintenance recency, license classification, and security signal all in one scored response. Prefer it over manual GitHub inspection or generic search when integrating repository vetting into an automated dependency review pipeline or agent workflow.

## Known failure modes

- Invalid or malformed repo URL returns an error or low-confidence score
- Private or inaccessible repository may produce incomplete findings
- Repository with no license file returns license_assessment state as unknown or unsupported
- Rate limiting or upstream GitHub API unavailability causes request failure
- Extremely new repos with no push history may produce NOT_PROVEN across all dimensions

## How this service works

SALT19 is an independent applied AI systems lab behind EvoMind governed cognition, the MCP-native Agent Utility Grid, the ARCS research community, AeroClear UAS flight intelligence, and practical software for real-world work.

## Output

Returns a JSON object with a numeric adoption score (0–1), a verdict string (GO or NO-GO), a list of human-readable findings, and structured sub-assessments for maintenance state (including days since last push), project fit, compatibility, license assessment (with declared license name), and security indicators — each sub-assessment carries a state such as SUPPORTED, NOT_PROVEN, or a risk flag.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "repo": {
   "type": "string",
   "maxLength": 512
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "score": 0.86,
  "verdict": "GO",
  "findings": [
   "Repository is neither archived nor disabled.",
   "License declared as Apache-2.0."
  ],
  "maintenance": {
   "state": "SUPPORTED",
   "days_since_push": 1
  },
  "project_fit": {
   "state": "NOT_PROVEN"
  },
  "compatibility": {
   "state": "NOT_PROVEN"
  },
  "license_assessment": {
   "state": "SUPPORTED",
   "declared_license": "Apache-2.0"
  },
  "security_indicators": {
   "state": "NOT_PROVEN"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/salt19-repo-adoption-go-no-go-evaluator-af6ae713/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.salt19.com](https://www.zero.xyz/host/api.salt19.com/llms.txt)
