magogi/prod/: mgf-apiprobe-0.5.7 metadata and description
REST API verification — typed probes, checks, and findings. Sibling of mgf-common.
| author | Bassam Alsanie, mgf-apiprobe contributors |
| classifiers |
|
| description_content_type | text/markdown |
| keywords | api, contract-testing, httpx, openapi, rest, verification |
| license | MIT |
| license_file |
|
| metadata_version | 2.4 |
| project_urls |
|
| requires_dist |
|
| requires_python | >=3.11 |
Because this project isn't in the mirror_whitelist,
no releases from root/pypi are included.
| File | Tox results | History |
|---|---|---|
mgf_apiprobe-0.5.7-py3-none-any.whl
|
|
mgf-apiprobe
REST API verification — typed probes, checks, and findings.
Shape: Federation sibling of
mgf-common. The currentmgf-commonpin window is shown in this package's Codeberg registry — sourced frompyproject.tomlat release time, so this README can't go stale. (Per v2.6 DOC-01 / project-shape taxonomy. PAPER-38.)
mgf-apiprobe is the API-verification sibling of mgf-common.
It builds on mgf-common's settings, error, and observability primitives,
and adds:
- Probes — typed descriptions of an HTTP request + the expected response shape.
- Checks — pluggable verifiers that emit structured Findings (code, severity, root_cause, evidence, remediation).
- Suites — collections of probes that run async and produce a Report.
- AuthFlows — bearer / basic / api-key / cookie / custom; OAuth2 is a future add.
- Matchers — DSL for asserting response shape (format + semantic; IBAN, IMEI, E.164 included).
Install
pip install mgf-apiprobe
Optional extras (forward-declared):
pip install 'mgf-apiprobe[openapi]' # OpenAPI ingestion
pip install 'mgf-apiprobe[faker]' # Faker-backed factories
pip install 'mgf-apiprobe[signing]' # Cassette signing
Quick start
from mgf.apiprobe import Probe, Suite, BearerAuth
probe = (
Probe.get("https://httpbin.org/get")
.with_auth(BearerAuth(token="..."))
.expects_status(200)
.expects_json_shape({"url": str, "headers": dict})
)
suite = Suite([probe])
report = await suite.run()
print(report.to_human())
Standards
Conformance: L2 per mgf-doc-standard/docs/standards/. Per-rule audit ledger: docs/inprogress/MGF_STANDARDS_CONFORMANCE.md.
The L2 floor means every federation MUST rule applies, evidenced by the tracker: BaseAppSettings, AppError hierarchy, structured logging, redaction, py.typed, SemVer with the 0.x carve-out, ≥80% coverage gate, no secrets in cassettes/logs. The earlier "L1 — Production-Ready" framing in this README was the pre-v2.7 nomenclature; the current standards (per docs/standards/README.md §"Conformance levels for projects") define L1 — Lite / L2 — Standard / L3 — Strict with L2 as the federation-sibling baseline.
Layout
| File | Purpose |
|---|---|
DESIGN.md |
The design spec (≈ 1990 lines). WHAT we're building. |
HANDOFF.md |
Integration plan. HOW it ships as a sibling of mgf-common. |
LIFT_CHECKLIST.md |
Federation conformance acknowledgment. |
License
MIT. See LICENSE (TBD).