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

@evidtrail/cli

v1.2.1

Published

Auditable AI provenance and change signals from git — CLI and GitHub Action. An auditable ledger of AI provenance and change signals for your git repositories — honest about what git can and cannot prove.

Readme

@evidtrail/cli

Command-line interface for evidtrail — an auditable evidence ledger for AI-assisted software development.

Installation

npm install -g @evidtrail/cli

Usage

Quick start

evidtrail init      # config + commit hook + prepare script + CI workflow, nothing overwritten
evidtrail doctor    # is this clone safe to measure? shallow clone, hook, config, CI
evidtrail           # collect → analyze → report (same as `evidtrail run`)

Basic workflow

# Collect commits from last 90 days
evidtrail collect --since 90d

# Analyze collected data
evidtrail analyze

# Generate the Markdown report
evidtrail report

This workflow stays local. It records repository change signals plus declared, inferred, and missing provenance; it does not infer productivity, defects, causality, or developer performance.

To declare provenance for future commits, install the hook. Set EVIDTRAIL_MODE or configure a truthful defaultMode in .evidtrail.json; when no mode can be determined, evidtrail writes no trailer and preserves unknown.

evidtrail install-hooks

Commands

evidtrail collect

Collect commits and generate commit-stream.json

Options:

  • --repo <path> - Repository path (default: current directory)
  • --since <date> - Start date (ISO or relative like 90d)
  • --until <date> - End date (ISO or relative)
  • --scope <value> - default-branch (default) or all-refs
  • --ai-pattern <pattern> - Custom AI detection pattern (repeatable)
  • --default-branch <name> - Default branch name (auto-detect if omitted)
  • --out-dir <path> - Output directory (default: ./evidtrail-output)
  • --verbose - Verbose logging

evidtrail analyze

Analyze commit stream and generate metrics.json

evidtrail report

Generate human-readable reports from metrics

Options:

  • --out-dir <path> - Output directory containing metrics.json

Output Files

  • commit-stream.json - Normalized commit data with AI tagging
  • metrics.json - Scoped attribution, rapid-retouch, trend, and outcome metrics
  • report.md - Human-readable Markdown report

Run evidtrail --help for the complete command reference. The repository README documents metric contracts, optional GitHub PR outcomes, and GitHub Actions/GitLab CI comments.