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

@circlesac/lint

v26.9.2

Published

🔧 Zero-config lint, format, typecheck, and structure checks for Circles repositories, powered by Biome

Readme

@circlesac/lint

🔧 Zero-config lint, format, typecheck, and structure checks for Circles repositories, powered by Biome.

Consumers keep no lint or format configuration of their own. The shared Biome configuration ships inside this package and is passed to the bundled Biome on every run; the Circles overrides on top of Biome's defaults are suspicious/noExplicitAny: error and complexity/noStaticOnlyClass: off.

Usage

npx @circlesac/lint --all            # Biome check with fixes and formatting, then TypeScript
npx @circlesac/lint --all --no-fix   # read-only gate for CI and test scripts
npx @circlesac/lint --biome          # Biome only
npx @circlesac/lint check            # structure checks (Workers API set when wrangler.jsonc is present)
npx @circlesac/lint check --json

Repository scripts

{
  "scripts": {
    "lint": "lint --all --no-fix",
    "format": "lint --biome",
    "check": "lint check",
    "test": "bun run lint && bun run check && vitest run --coverage"
  }
}

Add the package as a dev dependency so the lint binary resolves: bun add -d @circlesac/lint.

check

Deterministic checks for what a linter cannot see. Every repository gets the generic set: Bun lockfile only, no neutralized gates (|| true), no latest or wildcard ranges, no exact version pins, the four scripts above, no scaffold leftovers, and no repository Biome config that weakens noExplicitAny. A repository with wrangler.jsonc also gets the Workers API set: wrangler types with the generated file ignored and not committed, no published Workers type package, controllers under src/controllers/<category>/ with index.ts and schemas.ts, one class per route with a static route and a static handle, validated inputs only, /openapi.json and /docs served from src/index.ts, tests calling the app-typed client built over app.fetch with an execution context, a Workers-pool runner config, and a README that links /docs with a Tooling section.

The command exits 1 on any failure, so bun run test gates on it.

Failure logs

When a tool fails, the full output is saved to $TMPDIR/circlesac-lint-<tool>-<timestamp>.log and, in GitHub Actions, appended to the step summary.