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

@waqashanifkhan/crawler

v1.2.0

Published

A crawler and actionable audit utility for SEO and GEO website analysis.

Readme

@waqashanifkhan/crawler

A TypeScript crawler and actionable SEO/GEO audit utility for public websites.

It can crawl internal HTML pages, inspect technical and on-page signals, then return a JSON-safe report with raw page data, prioritized issues, evidence, scores, and implementation steps.

Installation

npm install @waqashanifkhan/crawler

Crawl pages only

import { SiteCrawler } from "@waqashanifkhan/crawler";

const crawler = new SiteCrawler("https://example.com", {
  maxPages: 20,
  concurrency: 4,
  timeoutMs: 8_000,
});

const pages = await crawler.crawl();
const analysis = crawler.analyze();

console.log(pages);
console.log(analysis);

crawl() returns a CrawlPage[]. Each page includes its URL, status code, title, description, headings, links, canonical state, robots state, schema types, image accessibility data, delivery headers, and crawl timing.

Run a full actionable audit

import { auditWebsite } from "@waqashanifkhan/crawler";

const report = await auditWebsite("example.com", {
  maxPages: 20,
  concurrency: 4,
  timeoutMs: 8_000,
  maxAffectedUrls: 20,
});

console.log(report.scores);
console.log(report.summary.topPriorities);
console.log(report.recommendations);

The audit report is JSON-safe and contains:

  • scores: overall, technical, SEO, content, performance, accessibility, and security scores.
  • summary: crawl totals, issue counts, and the top five priorities.
  • pages: all crawled page-level data.
  • crawlAnalysis: robots.txt, sitemap, internal-link graph, duplicate metadata risk, canonical issues, orphan pages, and crawl-based performance estimates.
  • issues: grouped findings with severity, affected URLs, evidence, why the finding matters, and clear remediation steps.
  • recommendations: the same issues sorted into an implementation priority order.
  • pageAudits: each crawled URL with the related issues attached.

Recommendation format

for (const recommendation of report.recommendations) {
  console.log(`#${recommendation.priority}: ${recommendation.title}`);
  console.log(recommendation.whatToFix);
  console.log(recommendation.howToFix);
}

Notes and limitations

  • Performance numbers are crawl-based estimates. Validate them with Lighthouse and real-user Core Web Vitals before making performance claims.
  • The package reads the HTML returned to the crawler. Fully client-rendered, login-protected, or blocked pages may need browser-based testing too.
  • Respect website terms, robots.txt, rate limits, and applicable law when crawling websites.

License

MIT