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

@automovie/evidence

v0.3.4

Published

Evidence configuration and optional narrative lifecycle validation for AutoMovie productions

Readme

@automovie/evidence

Configures the evidence check of an AutoMovie production. A production's evidence.config.ts calls createEvidenceConfig, and @wrtnlabs/evidence then checks that the production's code, and its writing once narrative is set, answers the checklists in its contracts. A production created by automovie create already has this package and a working configuration.

Configure

To add the package to a project made another way, run npm install --save-dev @automovie/evidence @wrtnlabs/evidence and place the checklists it reads under .agents/skills. The package needs Node.js 22.23.2 or later.

import { createEvidenceConfig } from "@automovie/evidence";

export default createEvidenceConfig({ location: import.meta.dirname });

location is the production's absolute directory. With nothing else set, these engineering defaults apply, and the narrative checks are off:

| Declarations | Answer | | --- | --- | | Exported types, interfaces and classes under src/**/*.ts | contracts/development/design.md | | Exported functions and class methods under src/**/*.ts | contracts/development/implementation.md | | Exported test functions under test/**/test_*.ts | contracts/development/testing.md | | All of the above | contracts/development/common.md |

A declaration answers a checklist in its doc comment, with one @evidence <checklist>#<item> tag per item followed by the answer.

The bundled contracts are read from <location>/.agents/skills. A production inside a pnpm workspace, where the root holds the one shared skills tree, names that tree, absolute or relative to location:

import { createEvidenceConfig } from "@automovie/evidence";

export default createEvidenceConfig({
  location: import.meta.dirname,
  skills: "../../../.agents/skills",
});

The production's own contracts, work/** and language/**, hold the questions specific to that work and to its language, and live under <location>/docs/contracts in either layout.

Bundled story citations start at contracts/story. When upgrading, install the matching scaffold. For active answers to checklists that kept their names, drop the former shared/ prefix. Final-expression questions moved into principles/screenplay.md for sections and obligations/screenplay.md for whole-film comparisons. For example, shared/naturalness/realized.md#speech-yield is now principles/screenplay.md#speech-yield.

If the production supplied its own docs/contracts/language/naturalness/ questions, merge the ones it still uses into the corresponding screenplay files under docs/contracts/language/. Reconcile active answers with their current questions and respondents. Preserve the revision a closed review covered.

Narrative

Add narrative when the production writes a screenplay:

export default createEvidenceConfig({
  location: import.meta.dirname,
  narrative: {
    mode: "short",
    construction: { brief: "evidence", screenplay: "evidence" },
  },
});

construction checks how each layer is built from the one before it. Setting a layer to "evidence" turns its check on, and setting a finished layer back to "disabled" leaves the layers still running unaffected.

Long-route scripts answer for scene progression, draft exchanges and event coverage. On both routes, final wording is checked during screenplay construction. Each section answers principles/screenplay.md. Each comparison across the film in obligations/screenplay.md takes one file answer.

short is a brief under docs/body/brief followed by the screenplay, and long, the mode of a series, has four layers: settings, treatments, scripts and screenplay. A layer you leave out stays a disabled draft. The checks cover the complete work unless scope names the first part that a pilot covers.

The screenplay is one folder per film with one file per scene: docs/body/screenplay/<film>/NNN-<scene>.md for a short, and docs/body/screenplay/NNN-part/NNN-episode/NNN-<scene>.md for a series, where each scene file realizes one scene of its episode's script. Both depths are selected on either route.

none checks no narrative layer, for a screenplay no narrative pass writes, and takes no construction or scope.

Research and development contracts

With narrative.mode: "short", the first study under docs/research/ activates research by default. The top-level index alone does not activate it. Set research explicitly on other routes or when closing a research stage. Use development when a production builds entities, behaviors and scenes in code.

When composition Evidence opens for programmed scenes or films, it expects case sources under src/composition/scenes/catalog/, the film at src/composition/films/catalog.ts and the record at docs/acceptance/catalog.md. The catalog answers the composition checklist. Screenplay coverage comes from the production scenes and films. The director verifies the registered catalog plays and judges the tested conditions.

export default createEvidenceConfig({
  location: import.meta.dirname,
  research: "evidence",
  development: {
    entities: "evidence",
    behaviors: "evidence",
    composition: "evidence",
  },
});

| Option | Checks | Against | | --- | --- | --- | | research | Each study in docs/research/ | contracts/story/principles/research.md | | development.entities | Exports under src/entities/ | contracts/development/entities.md | | development.behaviors | Exports under src/laws/, src/interactions/ and src/consequences/ | contracts/development/behaviors.md | | development.composition | Exports under src/composition/ | contracts/development/composition.md, citing the screenplay scene files, sections and beats they realize |

When entities or composition are submitted, entity types cite the subject files in cast/, crowds/, props/ and sets/ under a short's docs/body/brief/ or a long work's docs/body/settings/. For example, @evidence docs/body/brief/props/ball.md The ball uses the brief's red panels.

Every screenplay section and beat must be realized by some scene, and every scene file by the film that orders it. Under narrative: { mode: "none" } with development.composition, every section of docs/instructions/ must be realized by some composition or entity too, with no exclusion, because no narrative layer cites them. An option you leave out stays disabled.

Your own claims

A claim binds a set of declarations to the checklist they answer. Top-level claims adds claims to the engineering defaults, and narrative.claims adds claims to the ones narrative configures. Both take IEvidenceClaim[] from @wrtnlabs/evidence.

createEvidenceConfig is the package's only entry. The @automovie/evidence/internal subpath serves this repository's own tests and tools and promises no stability.

Run

npm run evidence

The exit code is 0 for a complete analysis without errors, 1 for violations and 2 for an invalid configuration or incomplete analysis. npx evidence list prints the configured targets, npx evidence inspect <target> explains one, and npm run evidence -- --only <targets...>, optionally with --shallow, checks only those targets. The @wrtnlabs/evidence documentation covers addresses, annotations and fingerprints.

A passing check means the checklists were answered. Whether the writing and the delivered video are good is still decided in review.