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

promptometer-core

v1.2.0

Published

Zero-dependency prompt evaluation engine — scores, anti-patterns, adversarial tests, rewrites and harness-agnostic agent task assessment (assess). JS/Python parity.

Readme

promptometer-core

Zero-dependency prompt evaluation engine with JS/Python parity (0 ms, 0 tokens, no network).

  • analyze(prompt) — 8-dimension score, grade and anti-patterns for designed prompts (system prompts, templates).
  • assess(prompt, context?) — evaluates the work request handed to an agent (typed by a person or emitted by an orchestrator). Harness-agnostic: the host passes context as data and assess() never touches the disk. (experimental, v1.2.0)
  • improve(prompt), runAdversarial(prompt), detectPatterns(prompt).

Install

npm install promptometer-core      # JS (browser, Node, Deno, Bun)
pip install -e packages/core       # Python, from this repo (adds the `promptometer` CLI)

assess()

const { assess } = require('promptometer-core');

const r = assess('edita auth/inexistente.py para validar el token', {
  known_files: ['src/auth.py', 'js/app.js'], // optional workspace index (e.g. `git ls-files`)
  turn: 1, is_voice: false, lang: 'es',      // all optional
});
r.quality;          // vague | moderate | specific | exemplary  (+ r.score 0-100)
r.targets;          // { mentioned, verified, missing, modules } — grounding against known_files
r.exploration_risk; // low | medium | high — qualitative blast radius
r.scope;            // { files, objectives, suggest_split } — anti mega-prompt
r.recommended_tier; // cheap | standard | deep — map it to your own models
r.correction;       // turn 2+: drift / correction detected
r.issues;           // [{ id: 'TA004', severity: 'high', message }] — stable ids TA000-TA010
r.tip; r.scaffold;  // one coaching tip + fill-in template when score < 50 ('' otherwise)

Python exposes the same function and output (import promptometer_core as pc; pc.assess(...)); keys come in both snake_case and camelCase.

CLI (JSON on stdout)

node promptometer-core.js assess "agrega tests a analyzer" --files-from git
python promptometer_core.py assess "reviértelo, te equivocaste" --turn 2 --lang en --compact

Parity

fixtures/assess-cases.json is the shared spec. python test_assess.py checks Python against it, checks that the regex/message spec embedded in the JS file (TA_SPEC) is in sync (--sync-js regenerates it) and compares both engines over the fixtures plus a randomized Unicode corpus.

MIT © j0sp0nc3