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

@wframe/core

v1.4.0

Published

Infer a protocol state machine from black-box agent sessions, compile a safe deterministic driver, and prove it. No LLM on the learned path.

Readme

@wframe/core

Infer a protocol state machine from black-box agent sessions, compile a safe deterministic driver, and prove it. No LLM on the learned path.

Part of Wireframe. Full documentation: https://wframe.org/docs

Install

npm i @wframe/core

Use

import { Recorder, infer, compile } from '@wframe/core'

// 1. Record a few successful sessions. No SDK, no source code.
const recorder = new Recorder()
recorder.observe(session)        // { steps: [{ verb, response }], outcome: 'success' }

// 2. Infer the protocol state machine (evidence-driven red-blue merging).
const model = infer(recorder.sessions)

// 3. Compile behind a coverage gate. Hold out some sessions to verify.
const { driver, report } = compile(model, { coverageGate: 0.95, heldOut })
if (!report.passed) throw new Error('coverage gate not met, keep recording')

// 4. Drive the learned path. Zero model calls. Escalate on anything unseen.
driver.start()
const r = driver.step(symbol)    // { action } or { escalate: true }

Versioned artifacts

Use compileArtifact when the driver must retain the evidence and settings needed for later maintenance:

import { compileArtifact, recompile, diff, probe, MockAdapter } from '@wframe/core'

const v1 = compileArtifact('inventory', training, {
  coverageGate: 0.95,
  heldOut,
})

// Save v1.artifact as JSON. It is also accepted by Driver.fromJSON().
const next = recompile(v1.artifact, newlyRecordedSessions)
if (!next.accepted) {
  console.error(next.refusal, next.report)
  process.exit(1)
}

// next.artifact is version 2 and its parentHash is v1's contentHash.
const compatibility = diff(v1.artifact, next.artifact)
process.exitCode = compatibility.exitCode

// Probes replay only the sessions supplied here.
const live = await probe(v1.artifact, new MockAdapter(), selectedProbeSessions, {
  maxSteps: 3,
})

Public maintenance signatures:

compileArtifact(protocol, training, options)
loadArtifact(json, options?)
resolveArtifactAbstraction(artifact, baseAbstraction?)
driverContentHash(driver, abstractionConfig?)
recompile(parentArtifact, newSessions, options?)
diff(oldArtifact, newArtifact)
probe(artifact, adapter, sessions, options?)

Artifacts keep the driver fields at the top level and add manifest, corpus, and settings. This means existing Driver.fromJSON() calls continue to work. loadArtifact() also upgrades an old bare-driver JSON document in memory as version 1 and computes its content hash. For legacy recompilation, pass the old corpus with baseSessions if it is available.

recompile() deduplicates identical sessions and applies coverage, unsafe-continuation, and forward-ambiguity gates. A failed candidate returns accepted:false, the report, and the failed gate names. It does not return a replacement artifact.

diff() reports structural additions, removals, and relabels. Its interface verdict is compatible only when every old reachable goal, command, command route, and command successor meaning remains valid. exitCode is 0 for compatible and 1 for breaking.

probe() sends the commands in the caller-supplied sessions to a live adapter. Commands can have side effects. Selecting a read-safe corpus is the caller's responsibility. The probe stops a session at its first divergence and never sends a later command from that session. maxSteps limits the number of commands sent from each supplied session.

License

MIT