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

newman-reporter-kensho

v0.1.1

Published

Kensho reporter for Newman — turns Postman collection runs into kensho-results/ for the Kensho CLI. (Published for Newman's reporter discovery; the canonical name is @kaizenreport/kensho-newman.)

Readme

newman-reporter-kensho

A Newman custom reporter that emits Kensho v1 JSON. The Kensho viewer's HTTP step UI (request / response panes, headers, status badges) lights up automatically because every Postman item becomes a Kensho case with step.request / step.response populated.

Install

pnpm add -D newman-reporter-kensho @kaizenreport/kensho

(The package is published as newman-reporter-kensho so Newman's -r kensho flag discovers it. The canonical alias is @kaizenreport/kensho-newman.)

Run

newman run collection.json -r kensho
npx kensho generate
npx kensho open

What we capture

| Postman / Newman concept | Kensho field | | --------------------------------------------- | -------------------------------------------------- | | Collection name | case.behavior.epic (and project.name default) | | Folder name | case.behavior.feature, case.suite[] | | Item name | case.name, case.behavior.scenario | | Request (HTTP method + URL + body + headers) | step.request{} on a per-item HTTP step | | Response (status, body, headers, size, duration) | step.response{} on the same step | | Each pm.test(...) assertion | sub-step under the request with step.assertion{} | | Folder name like @blocker/Auth | case.severity = 'blocker' | | pm.environment.set('kensho_severity','critical') (pre-request) | case.severity | | pm.environment.set('kensho_tags','smoke api') (pre-request) | merged into case.tags[] | | console.log/warn/error from sandbox | case.logs[] | | 5xx with no assertion failure | case.status = 'broken' | | Failing assertion | case.status = 'fail' | | Skipped (pm.execution.skipRequest()) | case.status = 'skip' |

Stable ids hash fullName + 'collection://<name>' so the same item across iterations is correlated on the platform.

Reporter options

newman run collection.json -r kensho \
  --reporter-kensho-output kensho-results \
  --reporter-kensho-projectName "Acme API" \
  --reporter-kensho-projectSlug "acme-api"

Or via env: KENSHO_OUTPUT, KENSHO_PROJECT_NAME, KENSHO_PROJECT_SLUG.

Tagging conventions

Collection
└── @blocker / Auth          ← folder name → severity blocker for everything inside
    ├── login @critical       ← item name → severity critical, tag 'critical'
    └── refresh-token @smoke  ← tag 'smoke'

For free-form labels, use a pre-request script:

pm.environment.set('kensho_severity', 'critical');
pm.environment.set('kensho_tags', 'smoke regression');