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

@vmlts/jevlint

v0.1.0

Published

Write ESLint and oxlint rules as questions. Jev answers them.

Readme

@vmlts/jevlint

Write ESLint and oxlint rules as questions. Jev answers them for each node, and your code decides what to report.

npm i -D @vmlts/jevlint
export TYPESAFE_API_KEY=...

A rule

// team-rules.js
import { definePlugin, defineRule, noul, choice } from "@vmlts/jevlint";

export default definePlugin({
  name: "team",
  rules: {
    "descriptive-names": defineRule({
      on: "FunctionDeclaration, MethodDefinition",
      ask: noul("Does the function name describe what its body does?"),
      message: "Name does not describe the body",
    }),
    "actionable-todos": defineRule({
      on: "comments",
      ask: choice("How actionable is this comment?", {
        actionable: "a TODO that names what to do and where",
        vague: "a TODO with no concrete action",
        not_a_todo: "not a TODO at all",
      }),
      report: (a) => a.choice === "vague" && "TODO has no concrete action",
    }),
  },
});

Enable it like any plugin.

// eslint.config.js
import team from "./team-rules.js";
export default [{ files: ["**/*.js"], plugins: { team }, rules: { "team/descriptive-names": "warn" } }];
// .oxlintrc.json
{ "jsPlugins": ["./team-rules.js"], "rules": { "team/descriptive-names": "warn" } }

How a rule decides

| Field | What it does | |---|---| | on | An esquery selector, or "comments" for every comment in the file | | ask | noul(question) for yes or no, choice(question, options) for one of several, score(question, levels) for a degree | | state | What Jev sees for each node. Defaults to the node's source text. Receives text(), enclosingFunction(), sourceCode and filename | | threshold | noul: the least acceptable probability of yes, default 0.5. score: the least acceptable score | | message | Reported when the answer falls below the threshold | | report | (answer, ctx) => message or false. Replaces threshold and message. Required for choice |

A config can move the threshold: "team/descriptive-names": ["warn", { "threshold": 0.7 }].

Phrase a noul question as the property good code has. The rule reports when Jev says no.

Cost and speed

  • All matched nodes in a file go to Jev in one request per rule, ten nodes per request.
  • Every answer is cached by question and node text under node_modules/.cache/jevlint. A second run on unchanged code sends nothing. Set JEVLINT_CACHE_DIR to move the cache, and JEVLINT_LOG=1 to print token usage per request.
  • The first run on a file blocks the linter for one round trip, about one second.
  • When Jev cannot be reached, the plugin prints one line to stderr, reports nothing for these rules, and stops asking for the rest of the run. The lint run still passes.

Plugin options

definePlugin({ name, rules, model: "jev-latest", batchSize: 10, timeout: 8000, cacheDir })

For tests, pass judge (a function that answers a batch) and cache: new MemoryCache() so no request leaves the machine.

Limits

  • No autofix. Jev judges code, it does not write it.
  • No type information. oxlint plugins cannot see types.
  • Node 20.19 or 22.12 and later.