Check library
the checks a gate can require, built in and your ownSample data — sign in to see your repositories.
| Protects | Checks | State | Pushes · 30d | Stopped · 30d | Approved by |
|---|---|---|---|---|---|
| sample-co/checkout-service | Signed pushes | Reconnect requiredEnforcing | — | — | Not changed since connected |
| sample-co/inventory-api | Signed pushes | Reconnect requiredEnforcing | — | — | Not changed since connected |
| Check | Version | Runs on | Published | Action |
|---|---|---|---|---|
| Built in3 | ||||
| Signed pushesEvery push is signed by a known identity. | built in | 2 gates | ships with Pushgate | |
| Git metadataRecord the commit and repository for every push. | built in | 0 gates | ships with Pushgate | |
| Agent metadataRecord what the tool could observe about its agent context. | built in | 0 gates | ships with Pushgate | |
| Yours · signed policies0 | ||||
| Nothing published yet. | ||||
| Drafts · not signed, cannot run on a gate0 | ||||
| No unpublished changes. New check | ||||
A check you write is published as a signed policy release. Signing publishes it; adding it to a gate is a separate approval.
Untouched changes are discarded after 14 days. Imports and signed policies are kept.