
k6
k6Testing & qualityBy grafana ↗
GitHub repository: Within freshness window. Last successful check . Freshness policy ↗
Execute load tests and measure performance.
For your agent
Use k6 to execute load tests and measure performance.
Source-list workflow marking: Not marked in source list (source list)
Agent capability details have not yet been reviewed. Check the official documentation ↗
Example command
k6 --helpRun after following the project’s setup instructions. Local files, credentials, or a connected service may be required.
What it does
- Load test execution
- Performance metrics
- Scripted scenarios
Homebrew installs
k6 ↗Explicitly requested installation events
- 30 days
- 4,803
- 90 days
- 14,362
- 365 days
- 69,725
From Homebrew installations that report analytics. Includes package variants; counts are not unique users.
Homebrew: Within freshness window. Last successful check . Freshness policy ↗
Checked . Source dated . How installs are counted ↗
GitHub activity: Within freshness window. Last successful check . Freshness policy ↗
Repository activity
Commits per week · GitHub snapshot
Tap, hover, or use the arrow keys to inspect weekly commits. Weekly totals can extend beyond the selected dates; the latest week may be incomplete. All time includes up to 52 recorded weeks. Hourly data is unavailable.
Commands and capabilities are described from the project documentation. Repository statistics cover grafana/k6, which may contain more than the CLI. Listing a tool does not mean every command has been tested with every agent.


