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

@overengineered-solutions/eslint-plugin-portfolio

v0.3.0

Published

Portfolio-wide ESLint rules: OES observability doctrine (no-untyped-external-response) + Tailwind v4 bracketed-route CSS-drop guard (no-tailwind-arbitrary-in-bracketed-route).

Readme

@overengineered-solutions/eslint-plugin-portfolio

Portfolio-wide ESLint rules enforcing the observability doctrine documented in every portfolio repo's CLAUDE.md / AGENTS.md: silent-zero is the failure mode.

Install

pnpm add -D @overengineered-solutions/eslint-plugin-portfolio

This package lives on GitHub Packages. Even though it's published with --access public, GitHub Packages still requires a valid GitHub token for download — see feedback_package_visibility_rule.md for the gotcha.

For CI workflows in the overengineered-solutions org, grant permissions: packages: read and pass NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }} on install. For non-GitHub runners (Vercel, local dev), use a PAT with read:packages scope.

Wire into eslint.config.mjs

import portfolio from "@overengineered-solutions/eslint-plugin-portfolio";

export default [
  {
    plugins: { portfolio },
    rules: {
      "portfolio/no-untyped-external-response": "error",
    },
  },
];

Rules

no-untyped-external-response

Flags type casts (as X, <X>) and typed declarations (const data: X = ...) anchored on an await someResponse.json() or await someResponse.text() call.

The escape hatch is Zod parsing. Pipe the JSON read through Schema.parse(...) or Schema.safeParse(...) and the rule short-circuits.

Why

When wrapping an external API, the loop body assumes a response shape. If that assumption is wrong, the loop iterates 0 times and emits no logs, no errors, no signal. This produced a 4-PR debug cycle on 2026-05-12 (makeros #88 → #96) that a single Zod-validated wrapper would have collapsed into one PR.

This rule mechanically enforces Layer 1 of the observability doctrine. Layers 2 (first-call shape observability), 3 (iteration-boundary counts), and 4 (daily smoke) remain code-review responsibilities for now — those would need richer flow analysis to enforce mechanically.

Bad

const res = await fetch("/u");
const data = (await res.json()) as UserShape; // silent-zero waiting to happen

Good

const res = await fetch("/u");
const data = UserSchema.parse(await res.json()); // throws on shape mismatch
const res = await fetch("/u");
const parsed = UserSchema.safeParse(await res.json());
if (!parsed.success) {
  logSystemEvent({ kind: "api.shape_mismatch", payload: parsed.error.flatten() });
  throw parsed.error;
}

Versioning

Semver. Tag vX.Y.Z on a commit to trigger the publish workflow (see .github/workflows/publish.yml). The workflow asserts that the tag matches package.json before publishing.

See also

  • Sister package: @overengineered-solutions/test-kit
  • Memory (in the agent's persistent memory system): feedback_external_api_observability_doctrine.md