Skip to main content
← Back to list
01Issue
FeatureTriagedSwamp ClubPublicTeam
Assigneesskunk-ape

Relationships

#4778 Registry: an extension earns "verified repository" and an A scorecard while its source is not in that repository

Opened by randybias · 11/15/2026

Versions: swamp 20261114.210101.0; registry page https://swamp-club.com/extensions/@hmcrum/tls-cert-expiry (latest 2026.09.17.1), checked 2026-11-15.

What happens: @hmcrum/tls-cert-expiry lists its repository as https://github.com/hcrumpler/swamp-extensions, and the registry shows it as verified (repositoryVerified: true, repositoryVerifiedUrl the same URL). Its scorecard is an A (93%). But the repository does not contain the extension: its main branch (commit fd64670, checked today) has eol-lifecycle, juniper-policy, nfl-player-stats and statuspage, and nothing for tls-cert-expiry (no directory, no manifest, no model file, in any commit of the history we fetched). The published package's source exists only in the registry tarball.

What we expected: "verified repository" to mean the published source can be found in that repository, so a reader can review the code, its history and its tests, and file a fix against it. If verification only proves who controls the repository, then either:

  • the check also confirms that the repository holds the package (for example the manifest name, or the model files at the published version); or
  • the scorecard and the page say plainly that the repository is verified for ownership only and does not contain this package, and the scorecard credit for a verified repository is withheld until it does.

Shortest reproduction:

  1. Run swamp extension info @hmcrum/tls-cert-expiry --json: the output shows repositoryVerified: true and score.grade: "A".
  2. Clone https://github.com/hcrumpler/swamp-extensions and search it for tls-cert-expiry or tls_cert_expiry: no match.
  3. Run swamp extension pull @hmcrum/tls-cert-expiry: the source arrives from the registry only.

Why it matters: the verified badge and the A grade tell a user the code is open and reviewable at a known place. Here it isn't. A user who wants to read the code before running it, or to send a fix upstream, finds nothing to read or patch. The badge also lifts the scorecard of a package whose public source can't be inspected, which is the thing the badge is meant to vouch for.

02Bog Flow
✓OPEN◉TRIAGED○IN PROGRESS○SHIPPED+ 1 MOREASSIGNEDCLASSIFICATION

Triaged

11/16/2026, 3:26:47 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
skunk-ape assigned skunk-ape11/16/2026, 1:10:05 PM
Editable. Press Enter to edit.

system commented 11/15/2026, 9:14:18 PM

Classified automatically when this issue was filed.

  • Source: Swamp Club

If you feel this classification is incorrect, add a ripple to tell us so.

skunk-ape commented 11/16/2026, 3:31:12 PM

The repository URL check is working as intended, verifying that a repo URL is provided and that it is publicly accessible. I can understand how the score language could set an expectation that more verification is happening.

I've marked this as a feature and we will revisit it during our next focus round on extensions. Thanks for the report!

Sign in to post a ripple.