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

@agenteer/trust

v1.0.0-rc.2

Published

Agenteer trust layer: evidence records, structured output with retry, filesystem access guard, cross-check engine. Zero dependency on @agenteer/core.

Readme

@agenteer/trust

Trust layer for Agenteer. Four standalone modules you can use with or without the full runtime:

  • /evidenceEvidenceRecordSchema, YamlEvidenceStore, and MemoryEvidenceStore for append-only evidence records.
  • /structuredStructuredProvider, a native-first structured-output wrapper with text-parse retry fallback.
  • /accessDenylistChecker, snapshot, and diffSnapshots for filesystem policy and access auditing.
  • /crosscheckCrossCheckEngine for comparing primary and secondary structured outputs.

Zero runtime dependency on @agenteer/core — this package stays usable in plain Node projects that want evidence-style observability.

Install

npm install @agenteer/trust zod

Requires Node >= 20.

Evidence records

import { YamlEvidenceStore, type EvidencePutInput } from "@agenteer/trust/evidence";

const store = new YamlEvidenceStore({
  dir: "./.session/evidence",
  duplicates: "dedupe",
});

const record: EvidencePutInput = {
  evidence_version: 1,
  claim_refs: [],
  run: {
    timestamp: new Date().toISOString(),
    trigger: "agent",
    node_run_id: "nrun-123",
    lineage_id: "L-42",
  },
  tool: {
    name: "tsc",
    command: "tsc --noEmit",
    exit_code: 0,
  },
  result: {
    verdict: "pass",
    summary: "compile clean",
  },
  kind: "gate_check",
};

await store.put(record);

The store writes one YAML file per record, keeps stale markers append-only, and validates every write against EvidenceRecordSchema.

Structured output with retry

import { StructuredProvider, type ProviderLike } from "@agenteer/trust/structured";
import { z } from "zod";

const provider: ProviderLike = {
  modelId: "demo-text-model",
  async generate() {
    return [
      "title: Release checklist",
      "bullets:",
      "  - Verify docs",
      "  - Run tests",
      "  - Pack tarballs",
    ].join("\n");
  },
};

const Spec = z.object({
  title: z.string(),
  bullets: z.array(z.string()).min(3),
});

const structured = new StructuredProvider(provider);
const result = await structured.generate({
  systemPrompt: "Return a concise checklist.",
  userPrompt: "Summarize the release prep as three bullets.",
  schema: Spec,
  schemaName: "release_checklist",
  maxRetries: 2,
});

If the provider exposes native structured output, StructuredProvider uses it. Otherwise it falls back to text parsing with validation-aware retries.

Filesystem access utilities

import { DenylistChecker } from "@agenteer/trust/access";

const checker = new DenylistChecker({ extend: ["/tmp/secrets"] });

checker.assertAllowed("/tmp/project/notes.md");
console.log(checker.isAllowed("/etc/passwd")); // false

Use snapshot() and diffSnapshots() when you need before/after filesystem evidence for a scoped subtree.

Cross-check engine

import { CrossCheckEngine } from "@agenteer/trust/crosscheck";
import { StructuredProvider, type ProviderLike } from "@agenteer/trust/structured";
import { z } from "zod";

const makeProvider = (modelId: string, yaml: string): ProviderLike => ({
  modelId,
  async generate() {
    return yaml;
  },
});

const engine = new CrossCheckEngine(
  new StructuredProvider(makeProvider("primary-model", "max: 3")),
  new StructuredProvider(makeProvider("secondary-model", "max: 3")),
);

const report = await engine.run({
  systemPrompt: "Extract the retry budget.",
  userPrompt: "The config says the max retry count is 3.",
  schema: z.object({ max: z.number() }),
  schemaName: "retry_budget",
});

The outcome tells you whether the two passes agreed, disagreed on specific keys, or skipped because no secondary generator was configured.

License

MIT — see LICENSE.