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

@meronq/core

v0.1.0

Published

Canonical Engineering Model types and builders, plus the Meronq project handle. The surface an out-of-repo consumer builds against.

Readme

@meronq/core

The Canonical Engineering Model (CEM) types and builders, plus the Project handle.

This is the surface a consumer outside the Meronq monorepo builds against — a desktop plugin, a separate tool, another repo. Everything with real behaviour (scanning, memory, retrieval, embeddings) lives in packages that are not published: this one is deliberately small and mostly types.

npm install @meronq/core

What is in here

  • CEM primitives — defineEntity, defineRelation, defineEvidence, defineEvent, defineAction, defineResult, and the canonical layer set (ADR-0019). Pure types and builder functions: no store, no I/O, erased at runtime.
  • Project — identity for a project root (rootPath, resolved name).

What is not in here

Project.getInfo() reports identity only. It does not read .meronq/local, does not open memory.db, and does not run the scanner — initialized is not a live check. If you need project state, memory search, or CEM persistence, this package is not the way in; those live behind the MCP tool surface.

This is stated plainly because it has been mistaken for more than it is.

Versioning

Semver from 0.1.0. Below 1.0.0, a minor bump may still change the shape of an export; pin exactly if that matters to you. The published surface is exactly what src/index.ts re-exports — nothing else in the monorepo is API.

License

Apache-2.0