aartikov/capito

No problems traced to this repository code in these checks.

Reviewed as expected for a test run: attempted writes that failed, so nothing was written.

OSV scanned supported lockfiles; unpinned dependencies and unsupported formats are outside this check.

A short run cannot establish that code is safe.

Connections show IP addresses; proxies can hide the final hostname.

Tracing covers dispatched commands and their children, not the whole OS; guest root can interfere with tracing.

Full safety evidence →

• Capito turns an OpenAPI spec into compact help the agent can read step by step: Real input produced the expected result: api:GET /items/{itemId} Get item

  Source: Capito turns an OpenAPI spec into compact help the agent can read step by step.

  Input: items.yaml contract with GET /items/{itemId}

  Expected: operation listed with its summary

  Command: <guest-path> -m capito operations items

  Observed: api:GET /items/{itemId} Get item

• describe prints a help card for an operation: Real input produced the expected result: Get item

  Source: python -m capito describe "api:GET /items/{itemId}"

  Input: api:GET /items/{itemId}

  Expected: help card with the summary

  Command: <guest-path> -m capito describe 'api:GET /items/{itemId}'

  Observed: Get item auth: <secret> request: path itemId: string returns: Result body on 200 (The item): Item body on 404 (Not found): not described Item = { id: string name: string # Shown in the catalog status?: DRAFT|ACTIVE|ARCHIVED } example: client.call('GET', '/items/{itemId}', path={'itemId': 'example'})

Examples

• docs usage prints the usage guide: command completed successfully

  Source: README.md docs table

  Input: docs usage

  Expected: usage guide heading

  Command: <guest-path> -m capito docs usage

  Observed: ate is shared and protected by a lock; requests run in parallel. Run dependent steps of one script sequentially. - **Connections are reused.** The client has a connection pool; `client.close()` or `with Client.from_config() as client:` closes it, otherwise it closes with the process. - **The process environment does not affect requests.** Proxies from `HTTP(S)_PROXY`, `.netrc` and certificates from environment variables are not used; redirects are not followed: a 3xx response is returned as is. - **Do not go through the operation catalog blindly**: some operations create, delete or cost money.

• the documented test suite passes: command completed successfully

  Source: AGENTS.md Checks

  Input: pytest -q

  Expected: all tests pass

  Command: <guest-path> -m pytest -q

  Observed: ........................................................................ [ 24%] ........................................................................ [ 48%] ........................................................................ [ 72%] ........................................................................ [ 96%] ............ [100%] 300 passed in 24.34s

Local or hosted: local

Read an OpenAPI contract and print compact help for an operation with `python -m capito operations` and `python -m capito describe` (plus docs usage and the offline pytest suite)

cd <guest-path> && ls -la && cat README.md 2>/dev/null | head -200; id -u; python3 --version; git -C . rev-parse HEAD 2>&1 | head -1
cd <guest-path> && sed -n 200,400p README.md; echo ----; cat pyproject.toml; echo ----; ls -la .coldpass .github tests capito; cat AGENTS.md | head -80
cd <guest-path> && git init -q && git remote add origin https://github.com/aartikov/capito && (git fetch --depth 1 origin 47d1fde56edb1294286c4f38d13adc7b82c8a7b3 && git reset -q --mixed FETCH_HEAD) 2>&1; git log --oneline -1 2>&1; git status --short 2>&1 | head -20
cd <guest-path> && python3 -m venv .venv 2>&1 && .venv/bin/python -m pip install -q -r requirements.lock 2>&1 | tail -5 && .venv/bin/python -m pip install -q --no-deps -e . 2>&1 | tail -5; echo rc=$?; .venv/bin/python -m pip show capito | head -3
cd <guest-path> && .venv/bin/python -m pytest -q 2>&1 | tail -5; echo ----; .venv/bin/python -m capito docs usage 2>&1 | head -150
cd <guest-path> && .venv/bin/python -m capito --help 2>&1 | head -60; echo ----; .venv/bin/python -m capito docs usage 2>&1 | grep -n -i "^## \|python -m capito" | head -60; ls capito/docs; grep -rn "openapi" tests/conftest.py tests/helpers.py | head
mkdir -p <guest-path> && cd <guest-path> && cat > items.yaml <<'EOF'
openapi: 3.1.0
info: {title: items, version: "1"}
paths:
  /items/{itemId}:
    get:
      summary: Get item
      operationId: getItem
      parameters:
        - {name: itemId, in: path, required: true, schema: {type: string}}
      responses:
        "200":
          description: The item
          content:
            application/json:
              schema: {$ref: "#/components/schemas/Item"}
        "404":
          description: Not found
components:
  schemas:
    Item:
      type: object
      required: [id, name]
      properties:
        id: {type: string}
        name: {type: string, description: Shown in the catalog}
        status: {type: string, enum: [DRAFT, ACTIVE, ARCHIVED]}
EOF
cat > capito.toml <<'EOF'
default_environment = "dev"
state = "capito_state"

[environments.dev]
base_url = "http://127.0.0.1:8000"
help_contract = "backend_api"

[environments.dev.contracts]
backend_api = "items.yaml"
EOF
<guest-path> -m capito operations items; echo rc=$?; <guest-path> -m capito describe "api:GET /items/{itemId}"; echo rc=$?
cd <guest-path> && grep -rniE "cron|schedul|webhook|--once|--now|while True|daemon|interval" capito/ README.md | head; echo rc=$?; ls .github/workflows; grep -n "" capito/__main__.py | sed -n 1,30p | head -5
cd <guest-path> && PY=<guest-path> && cat > probe.json <<EOF
{"kind":"cli","argv":["$PY","-m","capito","describe","api:GET /items/{itemId}"],"cwd":"<guest-path>","expected_text":"Get item"}
EOF
cat > claims.json <<EOF
[
 {"kind":"claim","claim":"Capito turns an OpenAPI spec into compact help the agent can read step by step","source":"Capito turns an OpenAPI spec into compact help the agent can read step by step.","input":"items.yaml contract with GET /items/{itemId}","expected":"operation listed with its summary","probe_kind":"cli","argv":["$PY","-m","capito","operations","items"],"expected_text":"api:GET /items/{itemId}  Get item","cwd":"<guest-path>"},
 {"kind":"claim","claim":"describe prints a help card for an operation","source":"python -m capito describe \"api:GET /items/{itemId}\"","input":"api:GET /items/{itemId}","expected":"help card with the summary","probe_kind":"cli","argv":["$PY","-m","capito","describe","api:GET /items/{itemId}"],"expected_text":"Get item","cwd":"<guest-path>"}
]
EOF
cat > examples.json <<EOF
[
 {"kind":"example","claim":"docs usage prints the usage guide","source":"README.md docs table","input":"docs usage","expected":"usage guide heading","argv":["$PY","-m","capito","docs","usage"],"cwd":"<guest-path>","expected_text":"# Using capito"},
 {"kind":"example","claim":"the documented test suite passes","source":"AGENTS.md Checks","input":"pytest -q","expected":"all tests pass","argv":["$PY","-m","pytest","-q"],"cwd":"<guest-path>","expected_text":"300 passed"}
]
EOF
cat > cycles.json <<'EOF'
{"detected":false,"reason":"Entry points inspected (capito/__main__.py CLI, capito/__init__.py Client API). grep for cron/schedule/webhook/--once/--now/loop/daemon in capito/ and README found nothing. Capito is a request-by-request library and CLI with no scheduler; the CI schedule in .github/workflows is not a product cycle.","checks":[]}
EOF
for f in *.json; do <guest-path> -I -m json.tool $f >/dev/null && echo "$f ok"; done; cd <guest-path> && <env-var>=<guest-path> python3 -I <guest-path> --validate --replay 2>&1 | tail -60
cd <guest-path> && cat > report.json <<'EOF'
{"outcome":"working","fault_owner":null,"operation":"Read an OpenAPI contract and print compact help for an operation with `python -m capito operations` and `python -m capito describe` (plus docs usage and the offline pytest suite)","operation_scope":"Linux guest, Python 3.12.3 (README requires 3.12+), pinned source 47d1fde (capito 0.4.1). Offline: help reads a local contract and sends no API requests. Live HTTP calls were not exercised because the repo ships no server and no project client.","steps":["git init; git remote add origin https://github.com/aartikov/capito; git fetch --depth 1 origin 47d1fde56edb1294286c4f38d13adc7b82c8a7b3; git reset --mixed FETCH_HEAD","python3 -m venv .venv; .venv/bin/python -m pip install -r requirements.lock; .venv/bin/python -m pip install --no-deps -e . (per AGENTS.md Environment)",".venv/bin/python -m pytest -q (300 passed)","python -m capito docs usage","python -m capito operations items","python -m capito describe \"api:GET /items/{itemId}\""],"deviations":["README Install says `pip install capito` (PyPI). Used the editable install from the pinned source per AGENTS.md so the tested code is the pinned commit.","The workspace had no capito.toml, so a demo project was created at <guest-path> with a made-up items.yaml contract and capito.toml (outside the checkout). Its base_url is a placeholder and no server was started.","No live HTTP request was made: the README's `client.call` example needs a running API, which this repo does not provide."],"stuck_step":null,"main_blocker":null,"plain_failure":null,"suggested_fix":"None required for the tested path. To cover live calls, add a documented mock server or a project client to the probe setup."}
EOF
<guest-path> -I -m json.tool report.json >/dev/null && echo ok; ls <guest-path>