Open VSX Registry API vs Warnely

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%90.2%
Uptime · 30d100%83.3%
P50 · ms245334
P95 · ms6931375
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit10800 req/window · 10799 remaining100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open VSX Registry API vs Warnely: common questions

Which is more reliable, Open VSX Registry API or Warnely?

On our scheduled checks, Open VSX Registry API leads on measured uptime — Open VSX Registry API at 100% versus Warnely at 90.2% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Open VSX Registry API or Warnely?

Open VSX Registry API has the lower median latency in our checks — Open VSX Registry API responds in 245 ms versus Warnely at 334 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Open VSX Registry API and Warnely need an API key?

Neither needs a paid key — Open VSX Registry API is callable with no signup, and Warnely is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Open VSX Registry API and Warnely from the browser?

Only Open VSX Registry API is browser-friendly — it returns CORS headers over HTTPS. Warnely needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Open VSX Registry API and Warnely free for commercial use?

Open VSX Registry API has unclear commercial terms, and Warnely has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.