Trending repositories

Ranked by Attention Score: stars gained over the last 7 complete days

Period

Sort order

Tag

Filters (1)

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

6 repositories by Attention Score · Oct 28, 2026 – Nov 3, 2026 (UTC)

Language: Go
Tag: Load testing
Clear all

1.grafana / k6

A modern load testing tool, using Go and JavaScript

golang
load-testing
load-generator
javascript
es6
performance
+3 more

Go AGPL-3.032K total1.7K forks

+55 stars

from 32,064 · score 4.03

2.rakyll / hey

HTTP load generator, ApacheBench (ab) replacement

Go APACHE-2.021K total1.3K forks

+15 stars

from 20,739 · score 2.77

3.tsenart / vegeta

HTTP load testing tool and library. It's over 9000!

load-testing
go
benchmarking
http

Go MIT25K total1.4K forks

+8 stars

from 25,231 · score 2.20

4.codesenberg / bombardier

Fast cross-platform HTTP benchmarking tool written in Go

fast
http
cli
benchmarking
bombardier
go
+6 more

Go MIT6.9K total332 forks

+4 stars

from 6,846 · score 1.61

GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.

go
testing
testing-tools
devops
qa

Go Other license19K total102 forks

+2 stars

from 19,325 · score 1.10

6.fortio / fortio

Fortio load testing library, command line tool, advanced echo server and web UI in go (golang). Allows to specify a set query-per-second load and record latency histograms and other useful stats.

golang
golang-library
golang-application
performance
performance-testing
performance-visualization
+5 more

Go APACHE-2.03.7K total282 forks

+1 stars

from 3,739 · score 0.69

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.