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

@ng-census/core

v0.1.0

Published

Angular codebase analyzer engine. Returns data, never formats it.

Readme

@ng-census/core

The analyzer behind ng-census.

You probably want the CLI instead:

npx ng-census analyze

This package is for building your own tooling on the same engine — a CI bot, an editor extension, an MCP server. It reads an Angular project and returns data. It never prints, formats or exits.

import { analyzeProject } from '@ng-census/core';

const result = await analyzeProject({ projectRoot: '/path/to/angular/app' });

for (const entity of result.entities) {
  console.log(entity.id, entity.metrics.legacyControlFlow);
  for (const finding of entity.findings) {
    console.log(`  ${finding.rule} at ${finding.file}:${finding.line}:${finding.col}`);
  }
}

The shape of result is defined in types.ts, and every metric is defined exactly in RULES.md.

Two things to know before you store the output:

  • Raw observations, not conclusions. standaloneFlag: "absent" is what the decorator said. Whether that means standalone depends on run.angularMajor — from Angular 19 it does.
  • null is not 0. null means "could not be measured here"; 0 means "measured, and there were none". Charts must skip null.

Early (0.x): metric definitions may still change before 1.0. A change to what a metric means is listed as breaking in the changelog.

MIT licensed.