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

@021.is/spine-lint

v0.4.3

Published

Spine-specific AST checks that biome can't express: enum-over-string, ResponseDto enforcement, endpoint documentation, i18n key parity, no raw SQL. Runs in CI as the spine-lint job + locally via `spine-lint .`.

Readme

@021.is/spine-lint

Spine-specific AST checks that biome can't express. Runs in CI as the spine-lint job in the quality gate; also runs locally via spine-lint ..

Rules

| Rule | Severity | What | |---|---|---| | spine/enum-over-string | error / warning | Forbids inline string-literal unions (: "a" \| "b" \| "c"). Warns on repeated string-literal comparisons (x === "foo" ≥2 times). Locked. | | spine/route-returns-response-dto | error | Every Next.js route handler must go through withErrorHandling from @021.is/spine-errors/next OR explicitly call ok() / err(). | | spine/endpoint-documented | warning | Every route handler must have a JSDoc block above it. | | spine/i18n-key-parity | error | Every t("namespace.key") exists in every locale catalog under src/i18n/. Prevents the silent UX bug where production renders raw keys in foreign locales. | | spine/no-raw-sql | error | Blocks $queryRawUnsafe / $executeRawUnsafe. Use Prisma or $queryRaw\…`` tagged-template. |

CLI

spine-lint .                           # run all rules on src/**
spine-lint src/feature/event          # narrow to one path
spine-lint --rule spine/enum-over-string .
spine-lint --github .                   # emit GitHub Actions annotations
spine-lint --list-rules

Exit code 1 on any error-level violation. Used as a required check in the spine-quality-gate workflow.

Disabling for a single line

// spine-lint-disable-next-line spine/no-raw-sql — needed for the pg_stat query
await prisma.$queryRawUnsafe(`SELECT * FROM pg_stat_activity`);

(Disables ALL rules on the next line if no rule id given.) You must always include the WHY comment. PR reviewers + future-you will look there first.

Enum pattern (the rule you'll hit most)

// ❌ inline union
function setStatus(s: "active" | "inactive" | "deleted") { ... }

// ✓ const-as-object enum
export const STATUS = { ACTIVE: "active", INACTIVE: "inactive", DELETED: "deleted" } as const;
export type Status = (typeof STATUS)[keyof typeof STATUS];

function setStatus(s: Status) { ... }

Why const-as-object instead of enum:

  • Tree-shakable (TS enum compiles to runtime objects).
  • Pure values; no class machinery.
  • Plays nice with as const and Object.values().
  • Industry standard (TanStack, Next.js codebase, Vercel SDK).