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

@totemheart/audit-kit

v0.1.8

Published

Reusable cross-mechanism audit helpers extracted from Totemheart's own core test suite — real bounded-state invariants and stress-scenario drivers for downstream forks/apps.

Readme

@totemheart/audit-kit

Reusable cross-mechanism audit helpers, extracted directly from Totemheart core's own test/integration/cross-mechanism-friction.test.js — the same real assertions used to stress-test its 18 relational-friction mechanisms, packaged so a fork or a downstream app built on Totemheart can run the same discipline against its own scenarios.

Install

npm install totemheart @totemheart/audit-kit

Usage

import { Totemheart, Personality } from 'totemheart'
import { noBurst, noHijack, assertFiniteState, driveToRupture } from '@totemheart/audit-kit'

const ai = noHijack( noBurst( new Totemheart( { personality: new Personality() } ) ) )

ai.loveHateEngine.observe( 'u', { L: 1, H: 0 }, {} )
ai.loveHateEngine.observe( 'u', { L: 1, H: 0 }, {} )

const ruptured = await driveToRupture( ai, { userId: 'u' } )
console.log( 'Bond ruptured:', ruptured )

assertFiniteState( ai ) // throws with a real message on the first bounded-state violation

API

noBurst(ai)

Raises SensoryOverload's real rate-based burst threshold so a tight processInput() loop in a test doesn't trip the (unrelated) freeze early-return. Returns ai for chaining.

noHijack(ai)

Neutralizes AmygdalaHijack's early return so a test can reach mechanisms downstream of it (rupture, repair, grief...). Isolates the mechanism under test — not a claim about what AmygdalaHijack itself should do. Returns ai for chaining.

assertFiniteState(ai, assertFn?)

Checks every real PAD/cortisol/dissonance/egoHealth/budget/sleep-pressure scalar is finite and within its own documented real bounds. Throws on the first violation. Pass your own assertFn(condition, message) (e.g. bound to node:assert's ok) to integrate with your test runner's own reporting.

async driveToRupture(ai, { userId, hostileText, maxTurns })

Drives a real, deterministic hostile-turn loop against a LoveHateEngine bond and returns whether it actually ruptured within maxTurns (default 40).

License

MIT