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

@toolmark/lint

v1.0.0

Published

Static lint for Toolmark tool manifests: naming, descriptions, schemas and LLM-facing hygiene, with an optional TypeSafe judge.

Readme

@toolmark/lint

Static lint for Toolmark tool manifests: the toolmark lint CLI (and a programmatic lint()) checks what makes agents fail — bad names, missing or short descriptions, invalid input schemas, LLM-name collisions, too many tools per page, consequential actions without a hint. It reads manifests (a JSON file, or a live page's test hook through Playwright), not source code, so it works for any stack.

pnpm add -D @toolmark/lint

ESM only; Node ≥ 22.12. @playwright/test ≥ 1.63 is an optional peer (only for --url, which also needs Chromium: pnpm exec playwright install chromium).

pnpm exec toolmark lint --url http://localhost:5173/
pnpm exec toolmark lint --manifest tools.json --format json
# without installing:
npx -p @toolmark/lint toolmark lint --manifest tools.json
Usage: toolmark lint [options]

  --manifest <file>        Lint a manifest file (repeatable)
  --url <url>              Lint tools collected from a live page (repeatable)
  --storage-state <file>   Playwright storage state for --url
  --judge <spec>           Load a judge module (repeatable)
  --budget <n>             Tool-budget threshold (default: 40)
  --format <pretty|json>   Output format (default: pretty)

At least one --manifest or --url is required. Manifests (files and --url pages alike) are validated against @toolmark/lint/manifest.schema.json.

| Exit | Meaning | | ---- | ----------------------------------------------------------------------------------------- | | 0 | No error findings | | 1 | At least one error finding | | 2 | Usage or runtime failure (bad arguments, no input, invalid manifest, missing Playwright…) |

--judge <spec> loads and runs code: the named module (a path, or a package resolved from the current directory) is imported and executed as part of the lint run. Only pass modules you trust. @toolmark/judge-typesafe is the optional TypeSafe judge.

Guide (manifest shapes, rules, judges): docs/guides/lint.md.

Docs: Lint guide · API reference.

License

MIT