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

@kaizenreport/kensho-jasmine

v0.1.1

Published

Kensho reporter for Jasmine — writes kensho-results/ so the Kensho CLI can generate a rich HTML report.

Readme

@kaizenreport/kensho-jasmine

A Jasmine reporter that emits the canonical Kensho v1 JSON format. Works for standalone Jasmine runs and Karma (Jasmine is Karma's default test framework).

Install

pnpm add -D @kaizenreport/kensho-jasmine

Standalone Jasmine (3 lines)

// spec/helpers/kensho.js (or wherever you wire reporters)
import KenshoJasmineReporter from '@kaizenreport/kensho-jasmine';
jasmine.getEnv().addReporter(new KenshoJasmineReporter({
  project: { name: 'Acme API', slug: 'acme-api' },
}));

Then run as usual:

npx jasmine
npx kensho generate
npx kensho open

Karma (5 lines)

// karma.conf.js
const KenshoJasmineReporter = require('@kaizenreport/kensho-jasmine').default;
module.exports = (config) => config.set({
  frameworks: ['jasmine'],
  reporters: ['progress'],
  plugins: [{ 'reporter:kensho': ['type', () => new KenshoJasmineReporter({ project: { name: 'Acme Web', slug: 'acme-web' } })] }],
});

(Karma's plugin shape varies by version — for older Karma, register the reporter inside beforeEach(() => jasmine.getEnv().addReporter(...)) from a spec helper file added to config.files.)

Helper API — kensho.step / attach / label / link

import { kensho } from '@kaizenreport/kensho-jasmine';

it('checks out cart', async () => {
  await kensho.step('open cart', async () => { /* … */ });
  await kensho.step('apply discount', async () => {
    await kensho.step('verify total', async () => { /* nested */ });
  });
  kensho.label('team', 'growth');
  kensho.link('https://jira.example.com/browse/PROJ-123', { kind: 'jira', label: 'PROJ-123' });
  kensho.attach('/tmp/cart.png', { kind: 'screenshot' });
});

What we capture

| Jasmine concept | Kensho field | | --------------------------------- | --------------------- | | describe(...) chain | case.suite[] | | it('@critical login', …) tags | case.tags[], case.severity | | passed/failed/pending/excluded | case.status | | failedExpectations[] | case.errors[] + sub-step with step.assertion | | pending('blocker reason') | case.severity (extracted from reason) | | console.log/warn/error during a spec | case.logs[] | | kensho.step(…) | case.steps[] (nests) | | kensho.attach(path, …) | case.attachments[] (file copied to kensho-results/attachments/<id>/) | | kensho.label(k, v) / link(…) | case.labels{}, case.links[] |

Each case gets a stable id hashed from fullName + filePath for cross-run correlation.

Options

new KenshoJasmineReporter({
  output?: string,                 // default 'kensho-results'
  project?: { name, slug, url },
  severityFromTag?: boolean,       // default true — promote @critical tags
  runId?: string,                  // override the auto-generated id
  filePath?: string,               // fallback when Jasmine doesn't expose result.filename
})