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

evaris

v0.3.0

Published

Evaris CLI and TypeScript SDK — publish Inspect AI eval runs to Evaris.

Readme

evaris

Evaris CLI and TypeScript SDK — publish Inspect AI eval runs to a Evaris deployment and read the results back.

Install

npm install evaris        # local dependency
npm install -g evaris     # or as a global CLI

CLI

evaris publish <log-dir> --project <project-id>

Publishes the newest .eval log in <log-dir>: creates a run, uploads the artifact, and completes the run so Evaris ingests it. By default the command waits until ingest finishes.

--project <id>       Evaris project public id (env EVARIS_PROJECT_ID) — required
--api-token <token>  Personal access token (env EVARIS_API_TOKEN) — required
--api-url <url>      API origin (env EVARIS_API_URL, default: the Evaris cloud API)
--name <name>        Run name (default: derived from the log file name)
--timeout <seconds>  How long to wait for ingest to finish (default 180)
--no-wait            Return as soon as the run is queued for ingest

Create a personal access token in the Evaris web app under Settings → API Tokens; it is shown exactly once. The same page shows your project id for --project.

CI example

- run: npx evaris publish logs/ --project "$EVARIS_PROJECT_ID"
  env:
    EVARIS_API_TOKEN: ${{ secrets.EVARIS_API_TOKEN }}
    EVARIS_PROJECT_ID: ${{ vars.EVARIS_PROJECT_ID }}
    # Optional, for self-hosted: EVARIS_API_URL: ${{ vars.EVARIS_API_URL }}

Querying runs and samples

Every read command accepts --json — that is the shape scripts and coding agents should consume. All of them authenticate with --api-token / EVARIS_API_TOKEN exactly like publish.

evaris projects list --json                  # discover project ids
evaris runs list --project proj_x --all --json
evaris runs show <run-id> --json             # eval header, scores, metrics, warnings
evaris runs samples <run-id> --score fail --all --json
evaris runs sample <run-id> <sample-id> --epoch 1   # full sample incl. transcript + events

runs list can omit --project when the token can see exactly one project; otherwise the command prints the visible projects and asks for an explicit --project. Human-readable tables are printed by default; --all follows pagination (capped at 5000 rows), and runs sample always prints the full sample JSON — transcripts and event traces are rich documents, not table rows.

Programmatic use

import { publishInspectLogs } from "evaris";

const result = await publishInspectLogs({
  apiUrl: "https://evaris-api-prod.evaris-backend.workers.dev", // or your self-hosted origin
  apiToken: process.env.EVARIS_API_TOKEN!,
  projectId: "proj_...",
  logDir: "./logs",
  runName: "nightly-evals",
});