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

@sovereignsquad/gds-eslint-config

v6.8.0

Published

Custom ESLint rules for GDS consumers, exposed via `createGdsConfig(options)`. Flat-config only (ESLint 9+).

Readme

@sovereignsquad/gds-eslint-config

Custom ESLint rules for GDS consumers, exposed via createGdsConfig(options). Flat-config only (ESLint 9+).

import { createGdsConfig } from '@sovereignsquad/gds-eslint-config';

export default [
  ...createGdsConfig({
    allowedImports: ['some-approved-package'],
  }),
];

Rules

no-raw-design-values (always on)

Forbids raw color literals (#hex, rgb()/rgba()) and hard-coded spacing/radius values (padding: '16px', etc.) in feature UI code. Use GDS theme tokens instead. Exempts files under a theme/ or tokens/ path segment.

no-forbidden-ui-imports (always on)

Forbids importing from a fixed list of legacy/non-GDS UI sources (@radix-ui/*, tailwindcss, lucide-react, @/components/ui/*). Pass allowedImports (an array of exact import specifiers) for reviewed exceptions.

require-exported-jsdoc (opt-in via enforceExportedJsdoc: true)

Requires a leading JSDoc comment on top-level exported functions, consts, classes, and interfaces. Off by default (enabling it repo-wide against an unbackfilled codebase fails immediately); scope it to already-documented files via jsdocFiles (a glob array).

no-accent-as-background (opt-in via accentBackgroundVariables)

Flags a background/backgroundColor/background-color/bg declaration whose value references an accent-classed GDS token (issue #644's ACCENT_ROLES) -- meant to be scarce by 60-30-10 design intent, never a large-surface fill (issue #647).

import { createGdsConfig } from '@sovereignsquad/gds-eslint-config';
import { ACCENT_BACKGROUND_VARIABLES } from '@sovereignsquad/gds-eslint-config/generated-accent-background-vars.js';

export default [
  ...createGdsConfig({
    accentBackgroundVariables: ACCENT_BACKGROUND_VARIABLES,
    // Reviewed exceptions: small, scarce, high-signal fills (a CTA button, a badge,
    // an active-tab indicator) are the intended use of an accent token, not a violation.
    allowedAccentBackgrounds: ['--gds-brand-accent', '--gds-state-success'],
  }),
];

Off by default -- there is no built-in variable list, since the rule cannot see @sovereignsquad/gds-theme's classification without depending on it. Passing an explicitly empty accentBackgroundVariables: [] throws at config-build time rather than silently linting nothing; omit the option entirely to leave the rule off.

Static source scan only: it cannot see a dynamically computed CSS value (a string built by concatenation, or a CSS-in-JS function call whose argument isn't a literal) -- the same scope boundary no-raw-design-values already accepts.