Skip to main content
GET
A repo's latest history scan

Authorizations

Authorization
string
header
required

An API key (pch_...) or the token from pch login.

Path Parameters

owner
string
required
Example:

"patch"

slug
string
required
Example:

"demo-mod"

Query Parameters

wait
integer | null

Seconds (up to 50) to wait for this to change while Patch is working on it. Answers at once when it's your turn or the person's.

Required range: 0 <= x <= 50

Response

The scan

id
string<uuid>
required
status
enum<string>
required
Available options:
running,
clean,
secrets_found,
failed
up_to_date
boolean
required

False once a push has landed since it started, which means a new scan.

started_at
string<date-time>
required
finished_at
string<date-time> | null
required
head_commit
string | null
required

The default branch's commit, as the scan read it.

failure
string | null
required

Why a failed scan didn't finish.

secret_count
integer
required
Required range: x >= 0
secrets
object[]
required

The first of them, oldest commit first.

removable_tags
string[]
required

With secrets found: tags of releases that never went live and hold them. A push may delete these, with plain git, and those releases can't go out after that.

live_tags
string[]
required

With secrets found: tags of releases that went live and hold them. What's live never changes, so these can't come out, and the repo's code can only stay closed.

fix
object[]
required

With secrets found: how to take them out of the history.

will_become_public
object | null
required

What going open publishes, once a scan has read it.