Skip to main content
← Back to list
01Issue
FeatureOpenSwamp CLI
AssigneesNone

Relationships

#1197 Add a command to re-trigger repository verification (repositoryVerified)

Opened by sntxrr · 7/16/2026

Problem

After swamp extension push, an extension's repositoryVerified can be false even when the repository is public and reachable via the host's API. The registry verifies using unauthenticated host API calls (GitHub is 60/hr per IP, shared across publishers), so a transient rate-limit or propagation lag at publish time records false — and that result is cached for 7 days. There is currently no CLI command to force a re-check; the only documented triggers are changing the repository: URL or publishing a new version.

Concrete case

@sntxrr/career-ops@2026.07.16.1 recorded repositoryVerified: false at publish (repositoryVerifiedAt ~2 min after push), while GET https://api.github.com/repos/sntxrr/swamp-career-ops returns 200 with "private": false.

Proposed solution

A swamp extension reverify <name> command that forces the registry to re-run repository verification immediately (bypassing the 7-day cache) and prints the new status. Server-side rate-limiting is fine to prevent abuse.

Alternatives considered

  • Wait 7 days for the cache to expire (slow, and unclear whether it auto-heals).
  • Bump the version and re-publish solely to re-verify (pollutes version history for a metadata-only change).
  • Temporarily change the repository: URL and change it back (hacky; risks a wrong URL in between).
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

7/16/2026, 10:54:26 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.