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

@scalequality/check

v0.4.0

Published

ScaleQuality continuous code-maturity check for CI. Re-measures your repo on every build and fails the pipeline below your maturity line.

Readme

@scalequality/check

Continuous code-maturity gate for CI. On every build it asks ScaleQuality to re-measure your repo and fails the pipeline when maturity drops below your line, so quality regressions are caught before they merge.

npx @scalequality/check --token "$SQ_TOKEN" --project <projectId>

Get your token and project id from ScaleQuality: open a connected repo's diagnosis and Turn on continuous measurement. Store the token as a CI secret named SQ_TOKEN.

Options

| Flag | Env | Default | Meaning | |------|-----|---------|---------| | --token | SQ_TOKEN | — | Your SQ token (required) | | --project | SQ_PROJECT | — | ScaleQuality project id (required) | | --host | SQ_HOST | https://app.scalequality.io | API host | | --timeout | — | 600 | Max seconds to wait for the measurement | | --json | — | off | Print the raw result as JSON |

Exit codes: 0 passed (or track-only), 1 below the cutoff, 2 error.

CI examples

GitHub Actions (a step in your job):

- run: npx @scalequality/check --token "$SQ_TOKEN" --project <projectId>
  env:
    SQ_TOKEN: ${{ secrets.SQ_TOKEN }}

GitLab CI:

scalequality:
  image: node:20
  script:
    - npx @scalequality/check --token "$SQ_TOKEN" --project <projectId>

Any other CI: run the same npx @scalequality/check command, with SQ_TOKEN exposed as a secret/variable.

Measured coverage

Coverage is only real once the tests have run. If this job produces a coverage report, the check finds it and ScaleQuality shows measured line coverage instead of a directional estimate. Nothing to configure: run your tests with coverage before this step.

- run: mvn verify                     # writes target/site/jacoco/jacoco.xml
- run: npx @scalequality/check --token "$SQ_TOKEN" --project <projectId>

Recognised out of the box: JaCoCo (jacoco.xml), LCOV (lcov.info), Cobertura (coverage.xml, coverage.cobertura.xml), Istanbul (coverage-summary.json), Clover (clover.xml) and Go (coverage.out). Multi-module builds are summed.

The reports are copied into a temporary .sqreports/ folder so they survive the archive's build-output exclusions, and that folder is removed before the command exits — including when the job is cancelled.

Report somewhere unusual? Point at it in scalequality.properties at the repo root:

sq.coverage.reportPaths=ops/reports/jacoco-aggregate.xml

Full guide: https://scalequality.io/docs/continuous-measurement