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

@coder/aegis

v0.10.0

Published

Controlled A/B experiments on black-box coding agents: the aegis CLI (Go binary with embedded TS eval compiler and web UI) plus the @coder/aegis TypeScript eval-authoring facade

Readme

@coder/aegis

Aegis runs controlled A/B experiments on black-box coding agents. Each trial executes in an isolated sandbox behind a capture proxy that records the full model-traffic transcript; artifact bundles are graded offline and reported with paired statistics — so you can measure whether a skill, prompt, model, or harness change actually helps.

One install ships both surfaces:

  • The aegis CLI — a self-contained Go binary (embedded TypeScript eval compiler and web UI) that scaffolds, validates, runs, grades, and reports experiments.
  • The @coder/aegis library — the TypeScript eval-authoring facade with bundled type declarations, so EVAL.ts files get IntelliSense and can be executed directly with node.

Installation

npm install -g @coder/aegis
aegis --help

Compiling EVAL.ts eval layouts requires Node.js >= 24 on PATH.

Quick start

# Scaffold an eval workspace with a runnable starter layout.
aegis init my-evals && cd my-evals

# Check that the starter compiles and is well-formed.
aegis validate evals/example-hello

# Configure the model upstream once (credentials go to the OS keyring) …
aegis setup

# … then smoke-run one live trial end to end.
aegis run evals/example-hello --provider exec --smoke --confirm-budget --allow-unsafe-host-graders

The starter drives the real claude-code harness through the exec provider, so the smoke run additionally needs the claude CLI on PATH (verify with claude --version) and an Anthropic credential — either via aegis setup above or an ANTHROPIC_API_KEY/ANTHROPIC_AUTH_TOKEN environment variable.

Evals are authored in TypeScript — one EVAL.ts per experiment declaring the hypothesis, the agent under test, variants, graders, and a spend budget:

import { defineExperiment } from "@coder/aegis";

export default defineExperiment("my-experiment", (evals) => {
  // hypothesis, subject, variants, graders, budget …
});

Agent skills

The package ships its authoring guides as plain-markdown agent skills: read them from node_modules/@coder/aegis/skills/ or via aegis skills list and aegis skills get <name> (start with eval-authoring).

Learn more