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

@cognivia/core

v0.3.0

Published

Cognivia's Learning Genome + Session Report engine. The single diagnostics algorithm shared by the site, developer console, CLI, and MCP server.

Readme

@cognivia/core

Cognivia's Learning Genome + Session Report engine. Zero dependencies. The same algorithm behind the site, the developer console, the CLI, the MCP server, and the hosted /v1 API, so every surface returns identical diagnostics.

import { buildReport, renderText } from "@cognivia/core";
const report = buildReport(attempts);   // attempts = [{subject,question,answer,correct,latencyMs,confidence}]
console.log(renderText(report));

@cognivia/core/client is a thin client for the hosted API (set COGNIVIA_API_KEY).

The stateful genome (GET /v1/learners/:id/memory-state)

With a live key, memoryStateRemote(id) returns each concept's full seven-variable Learning Genome and a plain-language diagnosis:

import { memoryStateRemote } from "@cognivia/core/client";
const ms = await memoryStateRemote("alice");
const c = ms.concepts[0];
c.genome.lambda.value;        // forgetting rate (Bayesian posterior mean)
c.genome.lambda.ci95;         // [lo, hi] 95% credible interval
c.genome.retrieval_strength.value;
c.diagnosis.headline;         // e.g. "Confident misconception"
c.diagnosis.action;           // what to do about it
ms.genome.lambda_weighted_mean;  // whole-learner signature

Per concept the genome carries lambda, retrieval_strength, latency_index, confidence_gap, consolidation_efficiency, fatigue_susceptibility, and pattern_dominance, each with a basis naming its science. Concepts with too little history return status: "insufficient_evidence" and no genome. The full schema is in docs/openapi-v1.yaml.

MIT · Manik Maurya