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

impactlens

v1.1.1

Published

Static code graph scanner and ticket-driven briefing CLI for AI-assisted development. currently only supports php and js/vue

Readme

ImpactLens

⚠️ Before using ImpactLens, read: docs/support.md

It explains what PHP, JavaScript, Vue and Nuxt support actually covers, known limitations, and the maturity of each scanner.


ImpactLens scans a codebase into a queryable graph and maps ticket text to relevant code.

Ticket → Graph → Briefing

It helps you answer:

  • Where should I start reading code?
  • Which files are relevant to this ticket?
  • What breaks if I change this?
  • How does a UI action reach backend code?

In summary: ImpactLens helps developers and AI agents find the right place to start, reducing exploration time and improving navigation in large codebases.


Install

npm install impactlens

On install, the agent skill is written to .ai/impactlens/skill.md. Skip with IMPACTLENS_SKIP_SKILL=1. Re-run: npx impactlens install-skill.

npx impactlens --commands
npx impactlens --help

Quick Start

Scan repository

impactlens scan /path/to/repo --lang=both

Analyze ticket

impactlens ticket sqlite/Graph.sqlite
--ticket=tickets/issue.txt
--scopes=php,js


What it builds

  • PHP classes, methods, routes
  • Vue components
  • JS/TS modules
  • Imports and calls
  • HTTP links (frontend → backend when resolvable)

Main Commands

| Command | Purpose | |----------|----------| | scan | Build graph | | ticket | Ticket → briefing | | ai-context | Analyze one symbol | | change-impact | Blast radius | | architecture | Layer violations | | cycles | Circular dependencies |


Documentation

  • docs/support.md ← Read first
  • docs/quickstart.md
  • docs/config-setup.md
  • docs/commands.md
  • docs/graph-model.md
  • assets/agent-skill/SKILL.md — agent playbook (→ .ai/impactlens/skill.md on install)

License

ISC