Usage this month
Loading…
Plan
—
Last Scan
No scans yet
—
—
—
Quality score
0
Errors
0
Warnings
0
Info
Badge markdown
Violations
Quick Start ▼
0
See it work first (no key needed)
pip install perf-lint-tool then perf-lint scan your-plan.jmx. Same 53 rules, run on your machine, free at every tier — worth doing before you wire anything into CI.
1
Create an API key
Use the API Keys section below to generate a key. It's shown once — copy it immediately and store it as a GitHub Actions secret named PERF_LINT_API_KEY.
2
Add the Action to your repo
Drop the workflow file below into .github/workflows/perf-lint.yml. The Action installs perf-lint in CI, lints your scripts, and posts only scores — your script files never leave the runner.
3
Every PR is scored automatically
Results appear here as history. PRs get an automated score comment. Grab a badge URL from any result row to embed a live grade in your README.
# .github/workflows/perf-lint.yml
name: perf-lint
on: [push, pull_request]

permissions:
  contents: read
  pull-requests: write   # lets perf-lint post the PR score comment

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: markslilley/perf-lint-action@v1
        with:
          api_key: ${{ secrets.PERF_LINT_API_KEY }}
          paths: '**/*.jmx'
          min_score: '60'
API Keys
Copy your key now — it won't be shown again
Try it here
No key needed · nothing stored
Runs the same 53 rules as the CLI and the Action. The script is linted and discarded — not saved, not in history, no quota used. Before it is sent, it is scanned in your browser for credentials and personal data — if any is found the send is blocked and nothing leaves this machine. For a production script with real secrets, run the linter locally instead: pip install perf-lint-tool.
Loading the on-device scanner…
The score and every violation appear here.
Scan history
Score trend