Your Exchange / review
Review desk
Inspect the package, check the evidence, and record a decision for its exact digest. Scanning informs your review; it never replaces it.
Checking reviewer access…
Sign in with GitHubChecking registry health…
Inspect health ↗01 / On your desk
Packages to inspect
Search applies to packages loaded in this queue.
How review and signed publication work
The first 100 pending submissions are shown oldest first, followed by up to 100 recently approved releases. Approval requires a passing scan for the exact digest. Approval does not guarantee safety or publish a release.
Signing remains an operator workflow outside the browser. After approval or revocation, publish updated TUF metadata using the documented operator procedure. Never upload signing keys here.
Operator and signing documentation02 / Registry health
Signing backlog and worker status
Operational status has not been loaded.
This is a server-reported operational snapshot, not verification of signatures or confirmation that every installed client received a revocation.
Operational alerts
Recent activity (UTC)
Stored signing metadata
Expiry is advisory: signatures are not verified by this view. Missing, invalid or expired roles need operator attention; an expiring role should be refreshed before expiry.
Revocations awaiting signed publication
Publish updated signed metadata promptly. These identities remain in published targets despite the recorded review revocation.
03 / Trace a release
Publisher and review history
Look up an extension to inspect its recent history.
Submitted versions
Review actions
04 / Keep the conversation open
Open publisher appeals
Responding records an explanation only. Approval, rejection, revocation and signed publication remain separate actions.
Appeals have not been loaded.