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

@sentinele2e/cli

v0.1.0

Published

The unified `sentinel` command for [Sentinel](https://github.com/ZeeshanAmjad0495/sentinel-e2e) — the operator entry point. It scaffolds a project, runs your flows, and turns the emitted telemetry into a defect classification. The CLI is **driver-agnostic

Readme

@sentinele2e/cli

The unified sentinel command for Sentinel — the operator entry point. It scaffolds a project, runs your flows, and turns the emitted telemetry into a defect classification. The CLI is driver-agnostic: it depends only on @sentinele2e/ai + @sentinele2e/core/@sentinele2e/contracts and shells out to your project's test runner (npx playwright test), so it never imports a browser driver — your project owns that.

Install

npm install -D @sentinele2e/cli

Commands

sentinel init [dir] [--force]            # scaffold a starter project
sentinel run [pattern] [--config <p>] [--dry-run]
                                         # shell out to `npx playwright test`
sentinel analyze <run.jsonl> [--json]    # classify one run (exit 1 iff a real bug)
sentinel report [dir] [--json]           # aggregate a telemetry dir -> RunReport
sentinel --help | --version
  • analyze delegates to @sentinele2e/ai (rules-only, no API key) and exits 1 iff a real-bug verdict is present.
  • report reads every *.jsonl in dir (default config.telemetryDir), classifies each run, and prints a cross-run table (or --json). Exits 1 iff any run has a real bug; an empty/missing dir is not an error.
  • run builds npx playwright test -c <playwrightConfig> [pattern]. --dry-run prints the command and exits 0 without spawning (the offline-testable path). A real run spawns the runner inheriting stdio, then hints at sentinel report. A real spawn needs a project + installed browsers, so it is exercised manually, not in offline CI (spec §5).

Configuration — sentinel.config.json

JSON so the standalone node dist/cli.js bin can load it without a TypeScript loader. Missing file → defaults; no config is required for analyze/report.

| Field | Default | Used by | | ------------------ | ------------------------ | --------------- | | telemetryDir | test-results/telemetry | report | | testDir | tests | scaffold / docs | | runner | playwright | run | | playwrightConfig | playwright.config.ts | run |

RunReport — the dashboard contract

sentinel report --json emits a RunReport (schemaVersion, generatedFrom, runs[] of RunSummary, and cross-run totals). This JSON shape is the input contract the Sentinel dashboard (slice F) renders; both the CLI table and the dashboard read the same structure. The type is exported from the package barrel.

See the root README for the full Sentinel overview.