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

@docture/eval

v0.0.3

Published

Field-level scoring, hallucination detection and cost reporting for docture extraction runs.

Readme

@docture/eval

Grade an extraction run.

import { formatFailures, scoreExtraction } from "@docture/eval";

const result = await extractor.extract(pdf.bytes, Invoice);
const score = scoreExtraction(groundTruth, result.data);

expect(score.f1, formatFailures(score)).toBe(1);

The metric

Precision / recall / F1 over flattened leaf paths, with typed comparators. Whole-document exact match is reported too, but it is too blunt to steer by: one misread digit and every document scores zero, which tells you nothing about whether a change helped.

Every field lands in one of four buckets, and the distinction matters. A hallucination is not a typo:

| | | |---|---| | match | both present and equal under the right comparator | | mismatch | both present, different | | omission | ground truth has it, the extraction does not | | hallucination | the extraction invented it |

Comparators are chosen by type, then by path: numbers get a tolerance (default one cent), dates compare as days, strings get a similarity floor (default 0.9, which forgives an OCR slip in a long name without accepting a different name).

Arrays

Index-aligned by default, because for a table document order is meaningful and silently reordering rows would hide a real bug. Pass alignArraysBy: "id" when order is not meaningful.

Reporting

aggregate, formatScoreboard (stable Markdown, so a diff between runs is readable) and formatFailures, which never lets a truncated list read as a complete one.