Skip to content
Back to search

codspeed-plugin-marketplace

MarketplaceWorks with Claude CodeGitHub

CodSpeed is the all-in-one performance testing toolkit. Optimize code performance and catch regressions early.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/codspeedhq/codspeed with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/codspeedhq/codspeed'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/codspeedhq--codspeed/badge.svg)](/listings/codspeedhq--codspeed)

HTML

<a href="/listings/codspeedhq--codspeed"><img src="/api/listings/codspeedhq--codspeed/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

curl -fsSL https://codspeed.io/install.sh | bash

> [!NOTE] > The CodSpeed CLI officially supports Ubuntu 20.04, 22.04, 24.04 and Debian 11, 12. > Other Linux distributions may work, but are not officially supported.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 13 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "codspeed-plugin-marketplace",
  3. "owner": {
  4. "name": "CodSpeed"
  5. },
  6. "plugins": [
  7. {
  8. "name": "codspeed",
  9. "source": "./",
  10. "description": "Tools for accurate and reliable performance measurement and optimization"
  11. }
  12. ]
  13. }
README.md · README · 286 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <a href="https://codspeed.io/?utm_source=codspeed&utm_medium=readme">
  3. <picture>
  4. <source media="(prefers-color-scheme: dark)" srcset="https://codspeed.io/codspeed-logo-dark.svg">
  5. <source media="(prefers-color-scheme: light)" srcset="https://codspeed.io/codspeed-logo-light.svg">
  6. <img alt="CodSpeed logo" src="https://codspeed.io/codspeed-logo-light.svg" width="400px">
  7. </picture>
  8. </a>
  9. </p>
  10. <h3 align="center">Optimize code performance and catch regressions early.</h3>
  11. <p align="center"><a href="https://codspeed.io/login?flow=get-started&utm_source=github-readme">Get Started</a> · <a href="https://codspeed.io/docs?utm_source=github-readme">Documentation</a></p>
  12. <br/>
  13. <p align="center">
  14. <a href="https://github.com/CodSpeedHQ/codspeed/releases/latest"><img src="https://img.shields.io/github/v/release/CodSpeedHQ/codspeed" alt="Latest Release"></a>
  15. <a href="https://github.com/CodSpeedHQ/codspeed/releases"><img src="https://img.shields.io/github/downloads/CodSpeedHQ/codspeed/total?logo=github" alt="Downloads"></a>
  16. <a href="https://github.com/CodSpeedHQ/codspeed/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/CodSpeedHQ/codspeed/ci.yml?branch=main&logo=github&label=CI" alt="CI Status"></a>
  17. <a href="https://github.com/CodSpeedHQ/codspeed/blob/main/LICENSE-APACHE"><img src="https://img.shields.io/github/license/CodSpeedHQ/codspeed" alt="License"></a>
  18. <a href="https://codspeed.io/discord"><img src="https://img.shields.io/badge/chat%20on-discord-7289da.svg" alt="Discord Chat"></a>
  19. <a href="https://codspeed.io/?utm_source=badge"><img src="https://img.shields.io/endpoint?url=https://codspeed.io/badge.json" alt="CodSpeed Badge"></a>
  20. </p>
  21. [![Video Demo](./assets/readme-video.gif)](https://codspeed.io/?utm_source=github-readme)
  22. # Key features
  23. - 🎯 **<1% variance** in measurements using CPU simulation - no more flaky benchmarks.
  24. - 🔥 **Differential flamegraphs** to pinpoint exactly what got slower, commit by commit.
  25. - 💬 **PR comments & status checks** showing performance impact directly in your workflow.
  26. - 🛡️ **Merge protection** to block PRs that degrade performance beyond your threshold.
  27. - 🐍 **Multi-language support** for Python, Rust, Node.js, Go, C/C++ and more.
  28. - 🏠 **Run locally or in CI** - works on your machine and integrates with GitHub Actions, GitLab CI, CircleCI, and more.
  29. - 🔌 **Plug your existing benchmarks** in less than 5 minutes - works with pytest, vitest, criterion, and more.
  30. ## Installation
  31. ```bash
  32. curl -fsSL https://codspeed.io/install.sh | bash
  33. ```
  34. > [!NOTE]
  35. > The CodSpeed CLI officially supports Ubuntu 22.04, 24.04, 26.04 and Debian 12.
  36. > Other Linux distributions may work, but are not officially supported.
  37. ## Quick Start
  38. First, authenticate to keep your benchmark results linked to your CodSpeed account:
  39. ```bash
  40. codspeed auth login
  41. ```
  42. The simplest way to get started is to benchmark any executable program directly:
  43. ```bash
  44. # Benchmark a single command
  45. codspeed exec -- ./my-binary --arg1 value
  46. # Benchmark a script
  47. codspeed exec -- python my_script.py
  48. # Benchmark with specific instrument
  49. codspeed exec --mode walltime -- node app.js
  50. ```
  51. This approach requires no code changes and works with any executable. CodSpeed will measure the performance provide the instrument results.
  52. ## Deeper integration with harnesses using `codspeed run`
  53. For more control and integration with your existing benchmark suite, you can use language-specific harnesses. This allows you to:
  54. - Define multiple benchmarks and keep them versioned in your codebase
  55. - Scope benchmarks to specific functions or modules
  56. - Integrate with existing benchmark suites (pytest, criterion, vitest, etc.)
  57. ```bash
  58. # Using the Rust harness with criterion
  59. codspeed run cargo codspeed run
  60. # Using the Python harness with pytest
  61. codspeed run pytest ./tests --codspeed
  62. # Using the Node.js harness with vitest
  63. codspeed run pnpm vitest bench
  64. ```
  65. These harnesses provide deeper instrumentation and allow you to write benchmarks using familiar testing frameworks.
  66. ### Languages Integrations
  67. CodSpeed provides first-class integrations for multiple languages and frameworks:
  68. | Language | Repository | Supported Frameworks |
  69. | --------------- | ---------------------------------------------------------------- | ------------------------------------- |
  70. | Rust | [codspeed-rust](https://github.com/CodSpeedHQ/codspeed-rust) | `divan`, `criterion.rs`, `bencher` |
  71. | C/C++ | [codspeed-cpp](https://github.com/CodSpeedHQ/codspeed-cpp) | `google-benchmark` |
  72. | Python | [pytest-codspeed](https://github.com/CodSpeedHQ/pytest-codspeed) | `pytest` plugin |
  73. | Node.js | [codspeed-node](https://github.com/CodSpeedHQ/codspeed-node) | `vitest`, `tinybench`, `benchmark.js` |
  74. | Go | [codspeed-go](https://github.com/CodSpeedHQ/codspeed-go) | builtin `testing` package integration |
  75. | Zig (community) | [codspeed-zig](https://github.com/james-elicx/codspeed-zig) | custom |
  76. Need to bench another language or framework? Open [an issue](https://github.com/CodSpeedHQ/codspeed/issues) or let us know on [Discord](https://codspeed.io/discord)!
  77. ### CLI Harness: `codspeed.yml` configuration
  78. The CLI also offers a built-in harness that allows you to define benchmarks directly.
  79. You can define multiple `codspeed exec` benchmark targets and configure options in a `codspeed.yml` file.
  80. This is useful when you want to benchmark several commands with different configurations.
  81. Create a `codspeed.yml` file in your project root:
  82. ```yaml
  83. # Global options applied to all benchmarks
  84. options:
  85. warmup-time: "0.2s"
  86. max-time: 1s
  87. # List of benchmarks to run
  88. benchmarks:
  89. - name: "Fast operation"
  90. exec: ./my_binary --mode fast
  91. options:
  92. max-rounds: 20
  93. - name: "Slow operation"
  94. exec: ./my_binary --mode slow
  95. options:
  96. max-time: 200ms
  97. - name: "Script benchmark"
  98. exec: python scripts/benchmark.py
  99. ```
  100. Then run all benchmarks with:
  101. ```bash
  102. codspeed run --mode walltime
  103. ```
  104. > [!TIP]
  105. > For more details on configuration options, see the [CLI documentation](https://codspeed.io/docs/cli).
  106. ## Performance Instruments
  107. CodSpeed provides multiple instruments to measure different aspects of your code's performance. Choose the one that best fits your use case:
  108. ### CPU Simulation
  109. Simulates CPU behavior for **<1% variance** regardless of system load. Hardware-agnostic measurements with automatic flame graphs.
  110. **Best for:** CPU-intensive code, CI regression detection, cross-platform comparison
  111. ```bash
  112. codspeed exec --mode simulation -- ./my-binary
  113. ```
  114. ### Memory
  115. Tracks native heap allocations (peak usage, count, allocation size) with eBPF profiling.
  116. **Best for:** Memory optimization, leak detection, constrained environments
  117. **Supported:** Rust, C/C++, Python (3.12+), and Node.js programs that allocate
  118. through libc, jemalloc, or mimalloc.
  119. ```bash
  120. codspeed exec --mode memory -- ./my-binary
  121. ```
  122. ### Walltime
  123. Measures real-world execution time including I/O, system calls, and multi-threading effects.
  124. **Best for:** API tests, I/O-heavy workloads, multi-threaded applications
  125. ```bash
  126. codspeed exec --mode walltime -- ./my-api-test
  127. ```
  128. > [!WARNING]
  129. > Using the `walltime` mode on traditional VMs/Hosted Runners will lead to inconsistent data. For the best results, we recommend using CodSpeed Hosted Macro Runners, which are fine-tuned for performance measurement consistency.
  130. > Check out the [Walltime Instrument Documentation](https://docs.codspeed.io/instruments/walltime/) for more details.
  131. > [!TIP]
  132. > For detailed information on each instrument, see the [Instruments documentation](https://codspeed.io/docs/instruments).
  133. ## Usage In CI environments
  134. Running CodSpeed in CI allows you to automatically detect performance regressions on every pull request and track performance evolution over time.
  135. ### GitHub Actions
  136. We recommend using our official GitHub Action: [@CodSpeedHQ/action](https://github.com/CodSpeedHQ/action).
  137. Here is a sample `.github/workflows/codspeed.yml` workflow for Python:
  138. ```yaml
  139. name: CodSpeed Benchmarks
  140. on:
  141. push:
  142. branches:
  143. - "main" # or "master"
  144. pull_request:
  145. workflow_dispatch:
  146. permissions:
  147. contents: read
  148. id-token: write
  149. jobs:
  150. benchmarks:
  151. runs-on: ubuntu-latest
  152. steps:
  153. - uses: actions/checkout@v4
  154. # Set up your language/environment here
  155. # For Python:
  156. - uses: actions/setup-python@v5
  157. with:
  158. python-version: "3.12"
  159. - run: pip install -r requirements.txt
  160. # Run benchmarks with CodSpeed
  161. - uses: CodSpeedHQ/action@v5
  162. with:
  163. mode: instrumentation
  164. run: pytest tests/ --codspeed
  165. ```
  166. ### GitLab CI
  167. Here is a sample `.gitlab-ci.yml` configuration for Python:
  168. ```yaml
  169. workflow:
  170. rules:
  171. - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
  172. - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
  173. codspeed:
  174. stage: test
  175. image: python:3.12
  176. id_tokens:
  177. CODSPEED_TOKEN:
  178. aud: codspeed.io
  179. before_script:
  180. - pip install -r requirements.txt
  181. - curl -fsSL https://codspeed.io/install.sh | bash -s -- --quiet
  182. script:
  183. - codspeed run --mode simulation -- pytest tests/ --codspeed
  184. ```
  185. ### CircleCI
  186. CodSpeed supports CircleCI for repositories hosted on GitHub.
  187. Here is a sample `.circleci/config.yml` configuration for Python:
  188. ```yaml
  189. version: 2.1
  190. jobs:
  191. benchmarks:
  192. docker:
  193. - image: cimg/python:3.12
  194. steps:
  195. - checkout
  196. - run: pip install -r requirements.txt
  197. - run: curl -fsSL https://codspeed.io/install.sh | bash -s -- --quiet
  198. - run: codspeed run --mode simulation -- pytest tests/ --codspeed
  199. workflows:
  200. codspeed:
  201. jobs:
  202. - benchmarks
  203. ```
  204. Jobs authenticate with OpenID Connect (OIDC) automatically, so there is no token to store. Pull requests opened from a fork cannot mint an OIDC token: set the `CODSPEED_TOKEN` environment variable for those jobs, as described in the [CircleCI configuration documentation](https://codspeed.io/docs/integrations/ci/circleci/configuration).
  205. > [!TIP]
  206. > For more CI integration examples and advanced configurations, check out the [CI Integration Documentation](https://codspeed.io/docs/integrations/ci/).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.