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

@cogitatum/core

v0.3.0-alpha.1

Published

Parse and compile inquiry markup that makes selected reasoning structure explicit inside ordinary prose.

Readme

@cogitatum/core

Cogitatum is a lightweight markup language for making selected reasoning structure explicit inside ordinary prose. This package provides its deterministic parser and compiler for Node.js and browsers.

Public Alpha: 0.3.0-alpha.1, format 0.3.0.

npm install @cogitatum/core@alpha
import { parseDocument, compileGraph } from '@cogitatum/core';

const source = `- We are checking the deployment before changing the database.
  - [C @cause] The connection pool may be exhausted.
    - [G] The logs show connection acquisition failures.
`;
const graph = compileGraph(parseDocument(source));
console.log(graph.points, graph.bearings, graph.diagnostics);

Ordinary body stays in the source AST; only marked structure produces graph entities. supports records a positive bearing without certifying an inference or choosing its method.

Every Point and Bearing has a compilation-local key. Only authored Point anchors populate id; only authored route names populate a Bearing's handle. Graph references use { key, kind }. Keys must not be persisted as stable references across revisions or source units.

parseSource and compileSource support input modes; host mode compiles document-level Markdown cog fences independently. ESM; Node.js 22.12 or newer for development and CLI use.

Optional Alpha debugging APIs, compileGraphWithExplain and explainSource, add a compiler trace of recognition, emitted or rejected entities, and diagnostics. This trace explains compilation decisions; it does not assess reasoning or record inquiry history. Use AST and Graph IR for integrations that do not need it.

AST blocks keep their semantic fields only in annotation; source raw and block text are retained separately. Reparse older source to migrate from format 0.2.0. The compiler rejects ASTs with a different format version.

The package includes self-contained draft 2020-12 JSON Schemas for offline integration:

import astSchema from '@cogitatum/core/schemas/ast' with { type: 'json' };
import graphSchema from '@cogitatum/core/schemas/graph-ir' with { type: 'json' };
import explainSchema from '@cogitatum/core/schemas/explain' with { type: 'json' };

Schemas describe individual projections, not multi-unit envelopes. They check data shapes; reference integrity and agreement with source require compiler-level checks. Keys are opaque strings: their numbering is not an integration contract. Store application metadata separately from canonical compiler output.

Read the introduction, syntax, or try the playground.