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

terminull-plugin-api

v0.1.0

Published

Terminull plugin contract: manifest types + zod schemas for the 8 contribution points, the pluginApi semver gate, a programmatic plugin-directory validator, and a scaffolding generator.

Readme

terminull-plugin-api

The public plugin contract for Terminull — manifest types + zod schemas for the eight contribution points, the pluginApi semver gate, a programmatic plugin-directory validator, and a scaffolder.

Terminull is extended by plugins, never by patching core. This package is what a plugin author depends on to author and check a plugin against the exact contract the runtime enforces.

npm install terminull-plugin-api

Three entry points

| Import | Runtime | Contents | | ------------------------------- | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | terminull-plugin-api | pure (zod only — web-safe) | PluginManifestSchema + the 8 *ContributionSchema, LocalizedTextSchema, CONTRIBUTION_POINTS, PLUGIN_API_VERSION, and rangeSatisfies (the semver gate). | | terminull-plugin-api/validate | Node (node:fs) | validatePluginDir(dir) — the machine oracle behind terminull plugins validate. | | terminull-plugin-api/scaffold | Node (node:fs) | scaffoldPlugin({ point, name, targetDir }) — writes a validate-green package. |

The . entry is pure so it can ship inside a browser bundle; the /validate and /scaffold subpaths touch the filesystem and are Node-only.

Validate a plugin directory

import { validatePluginDir } from 'terminull-plugin-api/validate';

const res = validatePluginDir('./terminull-plugin-my-theme');
if (!res.ok) {
  for (const e of res.errors) console.error(`[${e.code}] ${e.at ?? ''}: ${e.message}`);
}

res is { ok, manifestSource, manifest, errors[], warnings[] }. ok is true only when errors is empty; warnings (e.g. the terminull-plugin-* name convention) never flip ok. Every error carries a machine code and, where relevant, an at path (contributes.themes[0].module) — actionable, not just "invalid". See the code table in docs/plugin-authoring/SKILL.md.

Scaffold a new plugin

import { scaffoldPlugin } from 'terminull-plugin-api/scaffold';

const { dir } = scaffoldPlugin({ point: 'themes', name: 'my-theme', targetDir: '.' });
// → ./terminull-plugin-my-theme, already passing validatePluginDir

First-class templates: themes, panels, locales. The other five points (adapters, renderers, keymaps, harnessForms, commands) share a generic template. Singular point names (theme) are accepted via normalizeScaffoldPoint.

The semver gate

import { rangeSatisfies, PLUGIN_API_VERSION } from 'terminull-plugin-api';
rangeSatisfies('^1'); // true  (host API major = PLUGIN_API_VERSION = 1)
rangeSatisfies('^2'); // false (fail-closed)

This is the exact function the Terminull runtime uses to admit or disable a plugin — authors check against identical code.

The contract in one page

The eight contribution points, the manifest JSON-schema, the semver rules, and one example per point live in the authoring kit:

  • Claude agents: docs/plugin-authoring/SKILL.md
  • codex / gemini: docs/plugin-authoring/AGENTS.md
  • one-screen summary: llms.txt at the repo root

License

MIT.