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

@kanaries/causal

v0.2.1

Published

[![npm version](https://img.shields.io/npm/v/%40kanaries%2Fcausal)](https://www.npmjs.com/package/@kanaries/causal) [![npm downloads](https://img.shields.io/npm/dm/%40kanaries%2Fcausal)](https://www.npmjs.com/package/@kanaries/causal)

Readme

@kanaries/causal

npm version npm downloads

Public npm facade for causal-js.

The current task workflow exposed through this package is production-scope within an explicitly bounded, DAG-first contract.

Primary entry points:

  • @kanaries/causal
  • @kanaries/causal/node
  • @kanaries/causal/web

Install:

npm install @kanaries/causal
pnpm add @kanaries/causal
yarn add @kanaries/causal
bun add @kanaries/causal

Quick start

Choose the smallest public surface that matches your use case:

  • @kanaries/causal: discovery algorithms, graph primitives, CI tests, and the DAG-first task workflow
  • @kanaries/causal/node: Node-specific runtime helpers
  • @kanaries/causal/web: browser-specific runtime helpers

Choose the right entry point

  • use the root facade when you want portable discovery or DAG-first workflow APIs
  • use the Node facade when you need runtime capability checks or worker helpers for Node.js
  • use the Web facade when you need browser capability checks or worker helpers for web runtimes

Example:

import { DenseMatrix, FisherZTest, pc } from "@kanaries/causal";

const data = new DenseMatrix(rows);
const result = pc({
  data,
  ciTest: new FisherZTest(data),
  alpha: 0.05,
  stable: true,
  ucRule: 0,
  ucPriority: 2
});

Pairwise additive-noise direction evidence is also portable across the root, Node, and Web entry points:

import { anm } from "@kanaries/causal";

const { forwardPValue, backwardPValue } = anm(x, y);

anm deliberately leaves orientation thresholds to the caller. Its default deterministic RBF regression is browser-safe and injectable, but is an intentional approximation rather than exact sklearn Gaussian-process parity.

Task workflow example:

import { CausalGraph, GRAPH_KIND, identifyEffect } from "@kanaries/causal";

const graph = CausalGraph.fromNodeIds(["X", "Y", "Z"], { kind: GRAPH_KIND.dag });
graph.addDirectedEdge("Z", "X");
graph.addDirectedEdge("Z", "Y");
graph.addDirectedEdge("X", "Y");

const result = identifyEffect({
  graph: graph.toShape(),
  treatment: "X",
  outcome: "Y"
});

console.log(result.estimandSpec?.expression);
console.log(result.backend);

Node runtime facade:

import { detectNodeRuntimeCapabilities } from "@kanaries/causal/node";

console.log(detectNodeRuntimeCapabilities());

Browser runtime facade:

import { detectWebRuntimeCapabilities } from "@kanaries/causal/web";

console.log(detectWebRuntimeCapabilities());

See the workspace root README, docs/tasks/end-to-end-workflow.md, and docs/v1-status.md for the current V1 scope, accepted parity boundaries, task-workflow example path, and release validation commands. For Step 3 workflow usage, also see docs/tasks/backend-selection.md and docs/tasks/operational-readiness.md.