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

@enc-protocol/plugin-contract

v0.9.0

Published

Universal plugin contract for ENC protocol apps. Slot types, Plugin discovery convention, registration helpers.

Downloads

120

Readme

@enc-protocol/plugin-contract

Universal plugin contract for ENC protocol apps. Provides:

  • Slot constants (Slots.RankerFn, Slots.EncryptFn, etc.) — the canonical string ids that match the Lean abbrevs the translator emits.
  • PluginSlot type descriptor — what every plugin package's slot export must look like.
  • verifyPluginRequires(slot, sample) — runtime check that an app's record shape satisfies a plugin's structural requirements.
  • discoverPlugin(mod) — extracts { slot, impl } from an imported plugin module (handles the convention of default-export OR named-export).

How to use as a plugin author

Your package looks like this:

// my-ranker/index.mjs
export const slot = {
  id: 'RankerFn',
  side: 'either',
  signature: 'Identity -> Store -> Post -> Int',
  requires: { record: ['likeCount', 'replyCount', 'createdAt', 'authorId'] },
};

export function rank(identity, store, post) {
  /* ... */
}

export default rank;

That's it. The runtime layer (SDK / dataview / enclave) imports your module, calls discoverPlugin, and registers impl against slot.id.

How to use as a runtime author

import { discoverPlugin, verifyPluginRequires } from '@enc-protocol/plugin-contract';
import * as rankerModule from '@enc-protocol/plugin-ranker-engagement';

const d = discoverPlugin(rankerModule);
if (d.ok) {
  // Optional: check the record-shape requirement before binding
  const sample = await store.firstRow('posts');
  const v = verifyPluginRequires(d.slot, sample);
  if (!v.ok) throw new Error(`incompatible: missing fields ${v.missing}`);

  sdk.registerPlugin(d.slot.id, d.impl);
}