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

@addiscorp/kit

v0.3.1

Published

The header, footer, theme and tool-site layout every Addis site shares, in each project's own brand colours.

Readme

@addiscorp/kit

The header, footer and theme every Addis site shares.

Menu structure = kit. Menu content = per app. The kit owns how the header, menu, footer and theme are built and how they behave; each app only says what's in them (its groups, items, buttons) and sets its brand colours. Nothing about one app's menu belongs in the kit.

Use it

npm install github:addiscorp/kit#v0.1.0
import '@addiscorp/kit/kit.css';
import { Header, Footer, HeaderButton, PersonIcon, themeBoot } from '@addiscorp/kit';

// In <head>, before paint: <script dangerouslySetInnerHTML={{ __html: themeBoot }} />

<Header
  brand={{ name: 'simien', mark: <img src="/mark.png" alt="" /> }}
  groups={[
    { id: 'docs', label: 'docs', items: [{ id: 'start', title: 'Start an app', href: '/docs/start/' }] },
    { id: 'menu', label: 'menu', items: [{ id: 'github', title: 'GitHub', href: 'https://github.com/simienapp' }] },
    { id: 'more', label: 'Matches', searchOnly: true, items: [/* found only by searching */] },
  ]}
  pathname={pathname}
  navigate={(href) => router.push(href)}
  Link={Link}          // your framework's link; a plain <a> by default
  start={<HeaderButton name="account" label="Account" variant="profile" icon={<PersonIcon />}>…</HeaderButton>}
  end={<>{/* notifications, settings, anything */}</>}
  placeholder="Search the docs"
/>

<Footer site="simien.dev" />

What the kit does, so no app has to

  • The menu: the brand button opens it; ⌘M / Ctrl+M opens and closes it; ⌘S, Ctrl+S or / opens it on search; typing anywhere searches; ↑ ↓ move, Enter opens, 1–9 open a numbered tile, Esc closes, ? lists the shortcuts. A click outside or a navigation closes it.
  • Groups are tiles (numbered 1–9 in order across groups) or rows (layout: 'list'); a searchOnly group appears only as search matches. An item has a href or an onSelect, an optional icon, detail and keywords.
  • HeaderButton: a round button with a popover, one popover open at a time with the menu: account, notifications (badge), settings, or anything else.
  • Footer: who makes the site (Addis Corp by default; owner changes it), the product's license when license is passed, the site's name, the light/dark switch.
  • Theme: themeBoot sets light or dark before paint (a theme cookie wins, else the system); ThemeToggle switches and remembers.

The license

Addis products are MIT (APS 17). One License describes a product's license, and the same value drives everything a site shows about it, so the footer, the badge, the page and the LICENSE file can't disagree.

import { LicenseView, MIT_LICENSE, mitLicense, type License } from '@addiscorp/kit';

const license: License = {};                                            // MIT, Copyright (c) 2026 Sami Fouad
const harar: License = { source: 'https://github.com/addiscorp/harar' }; // public: the source is linked
const p8: License = {                                                   // a fork keeps its upstream notices, above ours
  github: 'samifouad',
  upstream: [{ year: 2025, holder: 'Di Wu', github: 'wudi' }],
  preface: 'p8 began as a fork of php-rs by Di Wu.',
};

<ToolSite tool="harar" license={harar}>…</ToolSite>       // footer: "MIT · © 2026 Sami Fouad" → /license/, then "source"
<Hero … status="alpha" license={harar} />                 // ( Status: Alpha ) ( License: MIT ) above the buttons; License → /license/
<ProductPills status="beta" license={license} />          // the same pair on any other page
<DocsLayout … license={harar}>…</DocsLayout>              // the same footer line
<Footer site="…" license={license} />                     // any site's footer
<LicenseView product="harar" license={harar} note={…} />  // the page: summary line, note, source, the full text
  • mitLicense(license) is the LICENSE file's text, byte for byte (tested against harar's and p8's files); MIT_LICENSE is the default one.
  • source is only for a public repository. Without it nothing links to a repository and nothing says "open source".
  • note on the page is for what the product must add: a part that keeps an upstream license.
  • href moves the page from /license/.

Make it yours

  • Colours and fonts are variables. Set your brand's after importing kit.css:
    :root { --ak-accent: #9a6b0c; --ak-ground: #fafaf8; --ak-display: var(--font-display); }
    :root[data-theme="dark"] { --ak-accent: #e2b54a; --ak-ground: #0b0c0e; }
    --ak-ground, --ak-panel, --ak-menu, --ak-tile, --ak-ink, --ak-soft, --ak-accent, --ak-edge, --ak-header-bg, --ak-font, --ak-display, --ak-width, --ak-topbar-h.
  • One item drawn your way: renderItem={(item, { active, current, shortcut, layout }) => …}; return undefined to keep the kit's.
  • A different layout entirely: useMenu({ groups, pathname, navigate }) is all the behaviour as a hook; wrap your own markup in <HeaderProvider menu={menu}> and use Launcher, MenuPanel, MenuItems, HeaderButton and ShortcutsHelp as you need them.

A tool's site

Every Addis tool (rixse, mirab, woreda, kebele, gelada, harar, p8, securecore, gild) gets the same site, after zega.dev: a hero with the install commands under the headline and a demo reel beside it, three benefits, the other Addis tools; and docs after rixse.dev. Structure = kit, content = per site: a site passes words, commands and demo lines, never markup of its own. The tools' marks and colours live here too, so every site and the family list agree.

import '@addiscorp/kit/kit.css';
import '@addiscorp/kit/tool.css';
import { ToolSite, Hero, Why, DocsLayout, Code, Step, Callout } from '@addiscorp/kit';

<ToolSite tool="mirab" Link={Link}>
  <Hero
    headline={{ before: 'Agents in VMs on ', accent: 'your own machine', after: '.' }}
    sub="The agent never holds a credential."
    github="https://github.com/addiscorp/mirab"
    installs={[{ label: 'install the cli', command: 'curl -fsSL https://mirab-releases.addis.gg/install.sh | sh' }]}
    reel={[{ title: '~/ops', caption: 'an agent is a folder', lines: [{ text: 'mirab init ops', kind: 'command' }] }]}
  />
  <Why tool="mirab" benefits={[…three…]} />
</ToolSite>

<DocsLayout tool="mirab" pages={[{ href: '/docs/', title: 'Overview' }]} pathname={pathname} title="Overview" lede="…" Link={Link}>
  …
</DocsLayout>
  • Status and license: nothing is 1.0 yet, so every tool's hero says where it stands and how it's licensed, in two pills of one shape, side by side above the buttons: ( Status: Alpha | Beta ) ( License: MIT ). The pills carry only that; anything longer goes in the words. ProductPills is the pair for any other page; StatusPill, LicensePill, statusText and LICENSE_PILL_TEXT are its parts.
  • The header is the mark, the name and docs. A tool that has more to link adds it after docs with links (p8: links={[{ label: 'test suite', href: 'https://p8-test-suite.addis.gg' }]}).
  • The reel is CSS only: its scenes play in turn, 5 s each, and each scene's lines appear one after another. With reduced motion it shows the first scene, still.
  • Colours: data-tool picks the tool's palette (src/tool/palettes.css, generated from its colour layout): one pale ground in light mode, a ground tinted with the brand in dark. The kit's footer and theme switch take the same colours.
  • Marks (MARKS, <Mark tool size />) are inline SVG for light and dark; the cut-outs between parts are var(--ak-cut), set to whatever is behind the mark.
  • Fonts: the site loads Urbanist, Instrument Sans and JetBrains Mono.

Develop

npm install
npm run typecheck
npm test          # builds dist/, then drives the header and footer in a DOM (jsdom)

License

MIT