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

Relationships

#1352 Website extension search ignores API relevance — exact name match "good-planning" ranks #10 (API ranks it #1)

Opened by magistr · 7/22/2026

Problem

On the swamp-club website, searching for good-planning returns the exact name match @magistr/good-planning only at position 10, behind unrelated extensions. The CLI/API ranks the very same query's exact match #1 — so the website is not applying the relevance ranking the API already computes. An exact (or prefix) name match should be at, or very near, the top.

Evidence (API vs web diverge)

API / CLIswamp extension search good-planning --json (20 results):

 1. @magistr/good-planning      <-- exact name match, ranked #1
 2. @goodcraft/github           (prefix "good")
 3. @goodcraft/stripe
 4. @goodcraft/customerio
 5. @goodcraft/vercel
 6. @goodcraft/bunny
 7. @goodcraft/forge
 8. @dougschaefer/google-meet-hardware
 ...

Identical ordering for the space variant good planning. The API relevance is correct: exact name first, then prefix-"good" matches.

Webhttps://swamp-club.com/extensions?q=good-planning (same ~20 results, different order):

 1. Doc Fact Checker
 2. Forge
 3. Aws Rds Reservations
 4. Scaleway Mongodb
 5. Rice Scoring
 6. Mongodb
 7. Seanime
 8. Livejournal Import
 9. Issue Lifecycle
10. Good Planning (@magistr/good-planning)   <-- exact name match, buried at #10
11. Manyfold Importer
 ...

The web order is neither relevance nor alphabetical — the exact-name result lands 10th while unrelated extensions top the list. It looks like the web search does not sort by the API's relevance score at all.

Proposed solution

  • Apply the same relevance ranking the API/CLI uses to the website search (ideally reuse the same search endpoint/ordering swamp extension search hits).
  • At minimum, boost exact and prefix name matches to the top so a query that equals an extension's name ranks it #1.

Alternatives

  • BM25 / trigram search with a strong weight on the name field over description.
  • Keep the current backend but re-sort the web result set by the API's relevance score before rendering (the API already returns them in relevance order).

Environment

  • swamp CLI: 20260720.142822.0-sha.0caa5556
  • Surface: swamp-club website extension search (https://swamp-club.com/extensions?q=...)
  • Repro query: good-planning (also good planning)
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

7/22/2026, 9:20:44 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.