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

@manya-hael/reflection

v1.0.0

Published

Evaluates outputs, critiques plans, and turns failures into lessons that force a revised plan — composed from memory and cortex.

Readme

@manya/reflection

Evaluates outputs, critiques plans, and turns failures into lessons that force a revised plan — not just a logged note nobody reads.

Composed from @manya/memory (where lessons live as semantic facts) and @manya/cortex (asked to re-plan once a lesson has been learned).

Usage

import { memory } from '@manya/memory';
import { createCortex } from '@manya/cortex';
import { reflection } from '@manya/reflection';

const store = memory.createMemoryStore('ara');
const cortex = createCortex(store);
const refl = reflection.createReflection(store, cortex);

reflection.evaluateAgainstIntent(refl, 'schedule a dentist appointment', 'Booked for Tuesday.');
// { passes: true, ... }

const { lesson, revisedPlan } = reflection.learnFromFailure(
  refl,
  'derive a key',
  'no passphrase was provided'
);
// lesson is now in semantic memory, and revisedPlan is a fresh cortex.plan()
// call made with that lesson already recorded.

Why this composition

The point of "learning from failure" is that the next plan is actually different. Reflection doesn't just write the lesson down — it immediately calls back into Cortex to produce a new plan, so the lesson has a chance to change the confidence score and steps of what happens next.