← Back to home
Comparison · Infra & APIs

Currents vs Harbor

A side-by-side editorial comparison of Currents and Harbor — release velocity, themes, recent moves, and the top alternatives to consider.

Currents vs Harbor: at a glance

FeatureCurrentsHarbor
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesplaywright, ci-observability, mcp, agent-accesscontainer-registry, cncf, security-patch, kubernetes
Last editorial update5d ago56m ago
WebsiteVisit →Visit →

What is Currents?

Currents opens every project on a health verdict: trend, state, and what to fix first.

Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API built for agents. The Oct 19 Project Overview adds a human-facing counterpart: projects now open on a page saying whether the suite is healthy, which way it is trending, and what to fix first.

Read the full Currents trajectory →

What is Harbor?

Harbor 2.14.6 RC2 adds Go CVE fixes on top of the regression rollbacks.

Harbor v2.14.6-rc2 keeps the rollbacks from RC1, so webhooks can reach private networks and legacy signer pulls are allowed by default, and adds Go dependency upgrades for High and Critical CVEs, Go 1.26.10, an actual byte limit in the CNAI parser to stop decompression attacks, and a nil-event panic fix in user audit. The 2.15 line got the same rollbacks in 2.15.4 RC1.

Read the full Harbor trajectory →

Currents vs Harbor: editorial side-by-side

C
Currents
INFRA · APIS
6.3

Currents opens every project on a health verdict: trend, state, and what to fix first.

◆ Current state

Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API built for agents. The Oct 19 Project Overview adds a human-facing counterpart: projects now open on a page saying whether the suite is healthy, which way it is trending, and what to fix first.

◆ Where it's heading

The product is converging on triage as its core job, for both audiences. Agents get granular paths into failures, traces and logs; humans get a prioritized summary instead of raw run lists. Both point at the same promise: Currents decides what to look at, not just stores results.

◆ Prediction

Likely next is linking Overview's fix-first items to the agent surfaces, so a prioritized problem can be handed straight to an MCP or trace-API session. The entries don't yet show that connection.

H
Harbor
INFRA · APIS
5.0

Harbor 2.14.6 RC2 adds Go CVE fixes on top of the regression rollbacks.

◆ Current state

Harbor v2.14.6-rc2 keeps the rollbacks from RC1, so webhooks can reach private networks and legacy signer pulls are allowed by default, and adds Go dependency upgrades for High and Critical CVEs, Go 1.26.10, an actual byte limit in the CNAI parser to stop decompression attacks, and a nil-event panic fix in user audit. The 2.15 line got the same rollbacks in 2.15.4 RC1.

◆ Where it's heading

Harbor's recent releases are split between security hardening and undoing the parts of that hardening that broke real deployments. Both supported lines now carry the rollbacks, and new work is CVE fixes rather than features.

◆ Prediction

Expect 2.14.6 and 2.15.4 finals shortly; the entries don't show a 2.16 feature release yet.

Alternatives to Currents and Harbor

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Currents or Harbor.

See all Currents alternatives → · See all Harbor alternatives →

Recent activity from Currents and Harbor

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoHarbor2.14.6 RC2: Go CVE fixes and decompression limit
  2. 7d agoCurrents[Improved] A better GitHub run comment
  3. 7d agoCurrents[New] Project Overview
  4. 12d agoCurrents[New] Trace API for agents ⚡
  5. 13d agoHarbor2.14.6 RC1: private-network webhooks and legacy signer pulls restored
  6. 18d agoHarbor2.15.4 RC1: rolls back webhook and signer-pull restrictions
  7. 19d agoCurrents[New] Run attachments
  8. 26d agoCurrents[New] Remote MCP Server with OAuth
  9. 1mo agoHarbor2.15.3 RC2: security fixes for proxy cache, uploads and exports
  10. 1mo agoCurrents[New] Personal Access Tokens
  11. 1mo agoHarbor2.15.3 RC1: security fix batch
  12. 3mo agoHarbor2.15.2 RC3: Valkey replaces Redis as cache backend

Frequently asked questions

What is the difference between Currents and Harbor?

They serve adjacent needs but don't currently overlap on shipped themes. Currents is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Currents better than Harbor?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Currents is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Currents?

Top Currents alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Currents alternatives" section above for the current picks, or visit /alternatives/currents-dev for the full list with editorial commentary on each.

What are the best alternatives to Harbor?

Top Harbor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Harbor alternatives" section above for the current picks, or visit /alternatives/harbor for the full list with editorial commentary on each.