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

@telic/lint

v0.1.1

Published

Taxonomy-governance CLI for @telic — lifts telic's runtime diagnostics to authoring time. Statically lints intent/command/handle/dispatch declarations for setter-like names, cross-file duplicates, scope ownership, and dead contracts.

Readme

@telic/lint

Taxonomy governance for @telic — lifts telic's runtime diagnostics to authoring time. A small, framework-agnostic CLI that statically lints your intent / command / handle / dispatch declarations so drift in the intent taxonomy is caught in review, not in production.

It uses the host's TypeScript compiler (a peer dependency, >= 5.5) — no bundled TS, no runtime dependencies.

npm install --save-dev @telic/lint
# or
bun add -d @telic/lint

Usage

telic-lint                       # scan **/*.{ts,tsx} from the current directory
telic-lint "src/**/*.ts"         # scan an explicit glob
telic-lint --json                # machine-readable findings
telic-lint --config telic.config.json

node_modules, dist, and .git are always excluded.

Exit codes: 0 = clean, 1 = findings, 2 = usage/config error.

Rules

| Rule | Trigger | Config to enable | |---|---|---| | setter-like-name | An intent / command / handle name whose post-dot segment starts with set / update / toggle / change (case-insensitive). Mirrors core S1.4 — name intents by the change the user intends, not the state you mutate. | always on | | duplicate-intent-name | The same name declared via intent(...) in more than one file (one finding per extra file). | always on | | scope-ownership | An intent / handle / command whose scope (first segment) is configured but whose file matches none of that scope's globs; and — under requireScopeOwnership — any scope not declared in config at all. | scopes / requireScopeOwnership | | dead-contract | A command("x") with no handle("x") anywhere scanned (warning — the handler may be presence-based/lazy), or a handle("x") with neither command("x") nor dispatch("x") (unused capability). | deadContract: true |

Only call sites in files that import from a specifier containing "telic" are eligible — unrelated local handle functions are never flagged. Aliased and namespace imports are resolved (import { intent as track }, import * as t from "@telic/core"; t.command(...)).

Config

telic.config.json, discovered upward from the working directory (or passed with --config). Everything is optional; a zero-config run enforces only setter-like-name and duplicate-intent-name.

{
  "scopes": {
    "checkout": ["packages/checkout/**"],
    "billing": ["packages/billing/**"]
  },
  "requireScopeOwnership": true,
  "deadContract": true
}

Scope globs are resolved relative to the config file's directory.

CI

telic-lint exits non-zero on findings, so it drops straight into a pipeline:

- run: bunx telic-lint --json > telic-lint.json || true
- run: bunx telic-lint          # fails the job (exit 1) if there are findings

Output is deterministically ordered by file then line, so --json diffs are stable across runs and machines.

License

MIT © Catalin Tanasescu