Repositories

Backed by: @pithy-sh/artifacts. Scopes: artifacts:repos:read · artifacts:tokens:revoke.

What it shows

Artifacts is the capability it reads, the TTL is the revocation window is why a token is worth taking back, the credential helper is how a git client gets one, and the reference has the routes behind every read and act here.

The git repositories your app hands its customers, and who holds a key to each, read live from your Worker. It appears in the rail beside Ledger when your Worker composes artifacts, at whatever path you mounted it.

The index lists repositories, a page at a time. Each row carries the display name your customers see, its owner (a person or an organization), whether git reaches it remotely, and when it was last pushed, or Never pushed.

The record is one repository. Its owner, remote access, last push, default branch, whether it is read-only, its clone URL and description when it has them, and when it was created. Under those come its tokens, its grants, and its commit log.

Grants list each person by id, and whether they pull, or push and pull. An owner needs no grant, so a repository with none says so.

Commits are the log, newest first and a page at a time: when, the short hash, the first line of the message, and the author.

Size is not shown. Cloudflare does not report it, and the pane does not estimate it.

Who holds each token

Every token Cloudflare lists on the repository, with its scope (Pull, or Push and pull), whether it is live, expired or revoked, when it was minted and when it expires. Cloudflare lists one page; when it holds more than it listed, the record says how many of how many.

Beside each token, where it came from, as your Worker answers it:

MintedWhat it says
By PithyMinted by the kit, for the holder it recorded
Outside PithyA warning. Something else issued it, such as Cloudflare’s dashboard, and no holder is recorded
UnknownMinted before the kit began recording, or its record has lapsed, so the kit may have minted it

A holder whose account was purged reads as a removed account, never as the stand-in id the kit kept in its place.

Taking a token back

Two acts: revoke one token, or revoke every live token on the repository. Each one previews exactly what it revokes, asks for a reason, and confirms once. Revoking every token names each live one it listed, and says how many more Cloudflare holds and did not list, because those are revoked too.

The git client holding a revoked token is refused on its next request. Anybody whose grant still stands mints a fresh one through the helper on their next operation; somebody whose grant is gone cannot.

Each press carries a key derived from what you were shown. A press whose answer was lost and is pressed again over the same preview gets Already done, and nothing is revoked a second time. A key already spent on a different revocation, or a token the repository no longer holds, is refused and says which. The record reads again after every revocation.

Each revocation is written to the dashboard’s own audit record: who did it, the repository, the tokens they were shown and the reason. Never a holder.

On every plan, and on Team

The reads render on every plan. Seeing a repository, its grants, its log and its tokens costs nothing.

The two acts are Team. Below it they are drawn locked, saying what Team buys.

Two scopes, a read and a write

artifacts:repos:read is every read here, and it is a read, so it is in the default grant. A connection without it sees the pane refuse by name and send nothing. Scopes has how to add one to a connection made before it existed.

artifacts:tokens:revoke is both acts, and it is a write, so it is never in the default grant. A connection without it shows the acts unavailable, with the scope they need.

It never creates, and it keeps nothing

Creating, forking and deleting a repository are not buttons here. Those belong to your own app.

Nothing here is kept. Repositories, grants, commits and tokens are fetched from your Worker for this screen and held in no Pithy table.

ESC