npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

qualink

v0.6.0

Published

Collect, normalize, and relay code quality metrics from CI

Readme

qualink

CI npm

Collect, normalize, and relay code quality metrics from CI. qualink standardizes code quality telemetry across repos and languages, then ships it to a sink (Elastic for now, if you need something else do a PR or a ticket).

Install

npm install -g qualink
pnpm add -g qualink
bun add -g qualink

Or run directly:

npx qualink collect eslint --input report.json --sink stdout

CI Examples

Repo, branch, commit SHA, pipeline run ID, and provider are auto-detected from CI environment variables, no need to pass them manually.

See the examples/ folder for copy-paste snippets for Azure DevOps and GitHub Actions.

Pipeline Tracking

Track pipeline execution metrics — which pipelines run, when, for how long, and their outcome. Pipelines self-report by calling qualink pipeline --status <status> at the end of a run.

Azure DevOps

steps:
  - script: echo "##vso[task.setvariable variable=PIPELINE_START]$(date +%s%3N)"
    displayName: Record start time

  # ... existing build/test steps ...

  - script: |
      END_TIME=$(date +%s%3N)
      DURATION=$(( END_TIME - $(PIPELINE_START) ))
      npx qualink pipeline \
        --status "$(Agent.JobStatus)" \
        --duration "$DURATION" \
        --sink elastic
    displayName: Report pipeline metrics
    condition: always()
    env:
      ELASTIC_URL: $(ELASTIC_URL)
      ELASTIC_API_KEY: $(ELASTIC_API_KEY)

Auto-detected from Azure DevOps env: pipeline name (BUILD_DEFINITIONNAME), trigger (BUILD_REASON), repo, branch, commit, run ID, provider.

GitHub Actions

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Record start time
        run: echo "PIPELINE_START=$(date +%s%3N)" >> "$GITHUB_ENV"

      # ... existing build/test steps ...

      - name: Report pipeline metrics
        if: always()
        run: |
          END_TIME=$(date +%s%3N)
          DURATION=$(( END_TIME - PIPELINE_START ))
          npx qualink pipeline \
            --status "${{ job.status }}" \
            --duration "$DURATION" \
            --sink elastic
        env:
          ELASTIC_URL: ${{ secrets.ELASTIC_URL }}
          ELASTIC_API_KEY: ${{ secrets.ELASTIC_API_KEY }}

Auto-detected from GitHub env: pipeline name (GITHUB_WORKFLOW), trigger (GITHUB_EVENT_NAME), repo, branch, commit, run ID, provider.

Per-stage reporting

For pipelines with distinct stages, call qualink once per stage with --stage-name:

# Azure DevOps example
- script: |
    npx qualink pipeline --status "$(Agent.JobStatus)" --stage-name build --duration "$BUILD_DURATION"
  condition: always()

- script: |
    npx qualink pipeline --status "$(Agent.JobStatus)" --stage-name deploy --duration "$DEPLOY_DURATION"
  condition: always()

CLI usage

Single collector

qualink collect <collector> --input <path> --sink elastic [flags]
qualink collect eslint --input eslint-report.json --sink elastic --repo frontend-mono --category frontend --tags frontend,web
qualink collect sarif --input analyzers.sarif --sink elastic --repo backend-api --category backend --tags backend,api
qualink collect coverage-dotnet --input coverage.cobertura.xml --sink elastic --repo backend-api

Multi-collect

Auto-discover report files in a directory tree:

qualink collect --dir=./output --repo myapp --sink elastic

Or use a config file for explicit control:

qualink collect --config=qualink.json --repo myapp --sink elastic

Config file example (qualink.json):

[
  { "type": "eslint", "input": "packages/*/eslint-report.json" },
  { "type": "coverage-js", "input": "packages/*/coverage-summary.json" },
  { "type": "sarif", "input": "**/*.sarif" }
]

Each entry supports optional overrides: tags, category, project, solution, url. See qualink-config.schema.json for the full schema.

Auto-discovery recognizes: eslint-report.json, biome-report.json, coverage-summary.json, coverage.cobertura.xml, *.sarif/*.sarif.json, lhr-*.json inside .lighthouseci/, junit.xml, and TEST-*.xml.

Pipeline tracking

Top-level command, not under collect:

qualink pipeline --status succeeded --sink elastic
qualink pipeline --status succeeded --duration 125000 --pipeline-name "Build and Deploy"
qualink pipeline --status succeeded --stage-name build --duration 45000
qualink pipeline --status failed --dry-run

Collectors:

  • biome (Biome JSON)
  • eslint (ESLint JSON)
  • lighthouse (Lighthouse JSON)
  • coverage-js (Istanbul/Vitest JSON)
  • sarif (Roslyn or generic SARIF JSON)
  • coverage-dotnet (Cobertura/OpenCover XML)
  • junit (JUnit XML)

ESLint file-level options (optional):

  • --top-files <n> adds top_files with the top offending files (default: 0, disabled)
  • --include-all-files adds all_files with every file that has lint issues

Classification metadata (optional):

  • --category for a single broad bucket
  • --tags for flexible multi-label filtering (comma,separated)

Project hierarchy (auto-detected or explicit):

  • --solution groups related projects (auto-detected from .sln or workspace root package.json)
  • --project identifies the individual project (auto-detected from nearest .csproj or package.json)

Metadata auto-detection:

  • repo: from flag/env, then git origin, then current folder name
  • branch: from flag/env, then git branch
  • commit_sha: from flag/env, then git commit
  • pipeline_run_id: from flag/env, fallback local-<timestamp>
  • project: from flag/env, then nearest .csproj/package.json
  • solution: from flag/env, then nearest .sln/workspace root package.json

If needed, you can still pass explicit values with --repo, --branch, --commit-sha, and --pipeline-run-id.

Sink configuration:

  • --sink elastic (default) requires ELASTIC_URL and ELASTIC_API_KEY
  • --sink loki requires LOKI_URL. Optional: LOKI_USERNAME, LOKI_PASSWORD (basic auth), LOKI_TENANT_ID (X-Scope-OrgID header for multi-tenant setups)
  • --sink stdout prints normalized documents for debugging

Dry run mode:

  • --dry-run validates and prints normalized payloads without sending to any sink

Useful env fallbacks:

  • QUALINK_REPO, QUALINK_CATEGORY, QUALINK_TAGS, QUALINK_BRANCH, QUALINK_COMMIT_SHA, QUALINK_PIPELINE_RUN_ID
  • QUALINK_PROJECT (auto-detected from nearest .csproj/package.json or PNPM_PACKAGE_NAME)
  • QUALINK_SOLUTION (auto-detected from .sln or workspace root package.json)
  • QUALINK_PIPELINE_PROVIDER (auto-detected, fallback: local)
  • QUALINK_ENVIRONMENT (default: ci)
  • QUALINK_SINK (default: elastic)