Skip to main content
← Back to list
01Issue
BugShippedSwamp CLI
Assigneeskeeb

Relationships

#497 extension search: empty results from CLI despite known extensions

Opened by webframp · 5/30/2026· Shipped 5/31/2026

Problem

swamp extension search consistently returns empty results regardless of the query, even though swamp extension info @swamp/aws/s3 and swamp extension pull work fine with the same registry.

Steps to Reproduce

swamp extension search aws --json
# Returns: {"query": "aws", "results": []}

swamp extension search "" --json
# Returns: {"query": "", "results": []}

# But this works:
swamp extension info @swamp/aws/s3 --json
# Returns full metadata

Expected Behavior

swamp extension search aws should return matching extensions from the registry (at minimum @swamp/aws/s3, @webframp/aws/cost-explorer, etc.).

Actual Behavior

Always returns {"query": "...", "results": []} regardless of query.

Environment

  • swamp version: 20260530.005533.0-sha.1c117111
  • Platform: macOS Darwin 24.6.0
  • Auth: authenticated as webframp
  • Registry: swamp-club.com
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

5/31/2026, 4:59:48 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
keeb assigned keeb5/31/2026, 4:07:37 AM
Editable. Press Enter to edit.

keeb commented 5/31/2026, 4:16:21 AM

Thanks for the report — I dug into this and currently can't reproduce it, and the registry looks healthy. A few things to help narrow it down:

I checked the server directly:

GET https://swamp-club.com/api/v1/extensions/search?q=aws
→ {"extensions":[…],"meta":{"total":373}}

An empty-query browse returns results too. I also ran the CLI at your exact version (…sha.1c117111) against prod, and both swamp extension search aws --json and swamp extension search "" --json returned full results.

One thing stood out: the output you pasted ({"query":"aws","results":[]}) has a results key, but neither the server response ({"extensions":…,"meta":…}) nor the CLI's --json output (query / extensions / meta) uses that key. That makes me suspect the output came from a different build than the version string suggests.

Could you share:

  1. The raw, unedited output of swamp extension search aws --json (no trimming).
  2. swamp --version and which swamp — to confirm the binary on $PATH matches the reported version (a stale/shimmed binary is a common cause).
  3. The registry host the CLI is actually hitting — any SWAMP_REGISTRY-style env var or config override, and whether you're pointed at swamp-club.com vs a self-hosted/alt registry.
  4. Whether it still happens. If it was a one-time blip, the extensions_search Atlas index may have been rebuilding when you hit it.

With the raw output + version/host confirmation I can pin down whether anything server-side needs fixing.

keeb commented 5/31/2026, 4:59:56 AM

Thanks @webframp for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.