cngx
cngx checks whether a coding agent actually ran the verification your policy requires before you trust its output.
pipx install cngx cngx quickstart
This tracker plots opt-in drift metrics from cngx submit. Each point is numeric fingerprint data (depth, verification steps, hedging, drift vs the submitter's own baseline). No prompts, no outputs, no personal identity collected or stored by the submit API.
community drift metrics
What you are looking at: how agents behave over time on real workloads, as reported by people who chose to share metrics.
- verification steps drops can mean the agent stopped checking its work (the failure mode
cngx checkcatches on a single response). - drift score rises when fingerprint shape diverges from that submitter's pinned baseline.
- A spike is a signal to investigate, not proof of regression.
live submissions: ...
Loading community metrics...
privacy
Submissions are opt-in. The API accepts only allowlisted numeric fields after you preview and confirm. Application code stores payload fields only (no prompts or outputs). Edge/API access logs may still exist at the infrastructure layer. The aggregated index at community/index.json is world-readable so this page can load it without a rebuild.