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

cortico

v0.1.6

Published

A TypeScript framework for event-driven, long-running persona bots

Readme

cortico

Framework sources for Cortico, published so that an extension package resolves cortico/* while it is being written.

An extension supplies one World, one provider or one bot, and imports the framework by its path under src/:

import type { WorldDefinition } from 'cortico/world.ts';
import type { EventEnvelope, WorldHost } from 'cortico/core/types.ts';

Inside a running instance those specifiers are resolved by the host's module hook to the framework that instance runs. This package supplies the same files to the editor, the type checker and the test runner. It has no entry point and starts nothing.

Install

pnpm add -D cortico

Each extension kind has its own contract version — world 5, provider 5, bot 5 — and a package declares its own as "cortico": { "kind": "world", "api": 5 } in its package.json. This package's minor version tracks the framework, so pin the range your extension was written against.

templates/extension/ in the repository holds a ready package for each kind, and docs/extensions.md states the packaging rules.

Running a bot

Deployments, bot packages and the web console live in a checkout of the repository, which is where a bot runs from: Quick Start.

MIT licensed.