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

@svashevchenko/ez-know

v0.5.0

Published

!!! Important: early development stage !!!

Downloads

709

Readme

ez-know

!!! Important: early development stage !!!

A business knowledge layer for your agents and your team.

You'll find it useful when:

  • You have a complex project with lots of entities, features and rules to govern them all;
  • Your agents break your apps when they miss some important spec;
  • Your team have a hard time answering questions like "Did we implement this right", "Does this feature conflict with existing rules and domains".

What's in the box

  • MCP server + agent skills
  • REST server + UI for human-friendly experience

Core concepts

Structured knowledge extraction

Domain
  -> Entity
    -> Entity Relationship
      -> Feature
         -> Capability
            -> Business Rule
               -> Constraint
                  -> Rationale
                     -> Evidence
                        -> Question

Every statement must have evidence And your codebase contains it all. Evidence can come from code,

And confidence in it is measurable.

Question is also a knowledge element

No direct knowledge base editing via model

Patch workflow

How to run

Install package globally with npm i -g @svashevhcenko/ez-know.

Shell commands:

  • ez-know for package overview and all important info;
  • ez-know init to install bundled skills, prompts for folder;
  • ez-know mcp starts the MCP server over stdio;
  • ez-know rest starts the REST service over the knowledge base with the web UI.

Add MCP server to your agent's config:

[mcp_servers.ez-know]
command = "ez-know"
args = ["mcp"]

[mcp_servers.ez-know.env]
EZ_KNOW_ROOT = "path/for/knowledge/files"
{
    "mcpServers": {
        "ez-know": {
            "command": "ez-know",
            "args": [
                "mcp"
            ],
            "env": {
                "EZ_KNOW_ROOT": "path/for/knowledge/files",
            }
        }
    }
}

Env config:

| env | default | desc | |----|---|-----| | EZ_KNOW_ROOT | ./ez-know relative to the current working directory | Knowledge root used by MCP, REST, patch drafts, and resource-backed tools. | | EZ_KNOW_REST_HOST | 127.0.0.1 | Host for the REST service. | | EZ_KNOW_REST_PORT | 3000 | Port for the REST service. Takes precedence over PORT. | | PORT | 3000 | Fallback REST port when EZ_KNOW_REST_PORT is not set. | | EZ_KNOW_LEGACY_RESOURCES | false | Enables legacy MCP fallback tools: list_mcp_resources, list_mcp_resource_templates, and read_mcp_resource. Any truthy value except 0, false, off, or no enables them. | | EZ_KNOW_PATCH_SCOPE_FILE_THRESHOLD | 100 | Maximum number of files per generated scope partition during patch scope and evidence coverage workflows. Invalid values fall back to 100. |

Example REST startup:

EZ_KNOW_ROOT=./ez-know ez-know rest