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

vidimus

v0.11.0

Published

Pre-publication checks for public static websites: accessibility, links, responsiveness, SEO, security headers, privacy, HTML validity, page weight, CSP, i18n, visual regression and Lighthouse.

Downloads

2,273

Readme

vidimus

npm node ci docs license

Vidimus, "we have seen": checks a static website's build before it goes public, and tells you how to fix what it finds.

npm i -D vidimus puppeteer pa11y linkinator
npm run build && npx vidimus
✖ noindex in the production build
    on: /en/search/ /fr/search/ /it/search/ +1 more
    → Remove the robots noindex meta tag, or add the path to seo.allowNoindex if it is intentional.

⚠ no <h1>
    on: /en/ /fr/ /it/ +1 more
    → Add one <h1> heading describing the page, or turn seo.h1 off.

Audits

| | | | --- | --- | | i18n csp seo security budget assets | read the build, no extra dependencies | | a11y links r12s privacy html shots lighthouse | run the tools you install next to vidimus (puppeteer, pa11y, linkinator, html-validate, lighthouse, sharp) |

i18n, csp, a11y, links and r12s run by default; npx vidimus all runs everything, npx vidimus seo budget runs just those. The default set needs puppeteer, pa11y and linkinator, installed above; the others are needed only by the audits that use them.

What each audit checks and its options: ljs360d.github.io/vidimus/audits.

Configure

npx vidimus init       # writes vidimus.config.ts
import { defineConfig } from 'vidimus';

export default defineConfig({
  siteUrl: 'https://example.org',
  audits: ['i18n', 'csp', 'a11y', 'links', 'r12s', 'seo', 'budget'],
  severity: { budget: 'warn' },
  ignore: [{ audit: 'seo', message: '^orphan page' }],
});

Adopting it on an existing site: npx vidimus --accept-findings records today's findings, and later runs fail only on new ones.

Client-rendered apps (React, Angular, Vue) work too: server.fallback answers their routes, routes lists or crawls them, and render audits the DOM the browser builds instead of the empty shell: client-rendered apps.

Docs

ljs360d.github.io/vidimus: getting started, how it works, audits, configuration, CLI, CI, frameworks, custom audits and API. Contributing: CONTRIBUTING.md.

The docs are deliberately built eight times from the same markdown, by VitePress, Starlight, Hugo, Eleventy, Zola, mdBook and client-rendered React and Angular apps, deployed side by side and audited by vidimus as one site, to dogfood it against eight builds' real output: why.

License

MIT