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

@krizaka/brief

v0.1.1

Published

A Krizaka product's weekly brief: a few figured recommendations, each with one action. The contract (integer money, named figures, evidence, assumptions), guards that veto with a reason, a deterministic ranking that keeps the top three, and the week in th

Readme

@krizaka/brief

A Krizaka product's weekly brief: a few figured recommendations, each with one action — « You have 5 free slots Thursday and Friday (450 $). 14 regulars have not booked for 6 weeks. [Invite them] ».

The product owns its data and its detectors; this block owns the contract, the guards, the ranking and the week.

import { composeBrief, isBriefDue, recommendation, weekOf } from "@krizaka/brief";

const { week } = weekOf(now, shop.timeZone);
const brief = composeBrief({
  week,
  ctx: snapshot,
  detectors: [gaps, pricing, taxProvision], // (ctx) => Recommendation[], pure
  guards: [{ name: "consent", check: (item, ctx) => (hasConsent(item, ctx) ? null : "NO_MARKETING_CONSENT") }],
}); // { items: top 3, vetoed: [{ item, guard, reason }], dropped }
  • Money is integer cents; figures are named integers; the words are the product's messages (keyed by kind).
  • id = <week>:<kind>:<subject>: the same data gives the same id, so an action is idempotent on it.
  • Ranking: urgency (now, week, info), then impact, then id — total and stable.
  • A guard (the falcon) vetoes with a reason; vetoed items are kept for the audit, never shown.
  • weekOf(instant, timeZone) and isBriefDue(instant, timeZone, lastSentWeek, { weekday: 1, hour: 7 }): an hourly scheduler asks; a missed Monday still sends later in the week.
  • No framework, no database, no environment, no wall clock.

Apache-2.0 · Krizaka TypeScript