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

@dep-radius/core

v0.4.11

Published

The library behind dep-radius: which changes in a dependency upgrade affect your code, and on which lines.

Readme

@dep-radius/core

The library behind dep-radius. It finds which changes in a dependency upgrade affect your code, and on which lines. Use it to build your own integration; for the command line, install dep-radius. The library guide: depradius.com/docs/library.

import { createCtx, defaultCacheDir, renderJson, run, type Options } from "@dep-radius/core"

const options: Options = {
  root: process.cwd(),
  specs: [],
  format: "json",
  offline: false,
  minAgeMs: undefined,
  latest: false,
  notes: true,
  surface: true,
  prod: false,
  concurrency: 8,
  cacheDir: defaultCacheDir(process.env),
  verbose: false,
  now: Date.now(),
  color: false,
}

const brief = await run(options, createCtx(options), (event) => {
  if (event.type === "package") console.error(`${event.done}/${event.total}`)
})

process.stdout.write(renderJson(brief))
process.exitCode = brief.exitCode

Entry points

| Import | Contains | | ---------------------------------------------- | ------------------------------------------------------------------- | | @dep-radius/core | run, createCtx, the brief types, renderJson, renderMarkdown | | @dep-radius/core/render | Grouping and labels, to write another renderer | | @dep-radius/core/schema/brief-v1.schema.json | The JSON Schema of renderJson's output |

The JSON output is a stable contract (schemaVersion: 1). The TypeScript types of the internal brief may still change before 1.0.

License

MIT