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

shipit-frontend-audit

v1.0.0

Published

Release-readiness checks for frontend projects before they go live

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

harfy345harfy345

Keywords

frontendwebwebsiteproductionreleaseauditreadinesscliseoaccessibilityperformancesecurity

Readme

ShipIt Frontend Audit

Release-readiness checks for frontend projects before they go live.

ShipIt reviews the project, runs its production build, and reports the work that still needs attention. Each finding explains what was detected, where to look, and how to fix it.

Install

Run it without installing:

npx shipit-frontend-audit audit .

Or install it globally:

npm install --global shipit-frontend-audit
shipit-frontend-audit audit .

Usage

Audit the current directory:

shipit-frontend-audit audit .

Audit another project:

shipit-frontend-audit audit ../my-website

Show the installed version:

shipit-frontend-audit --version

What It Checks

  • Build: package metadata, build scripts, dependency installation, TypeScript, build success, output files, and framework detection
  • Environment: environment files, ignored secrets, localhost URLs, and documented environment variables
  • SEO: titles, descriptions, viewport, canonical URLs, Open Graph, Twitter cards, language, favicon, robots, and sitemap files
  • Accessibility: image alternatives, button names, form labels, interactive elements, and duplicate IDs
  • Performance: large images, JavaScript bundles, CSS files, fonts, and production source maps
  • Security: likely secrets, unsafe HTML injection, insecure URLs, and npm dependency vulnerabilities
  • Production hygiene: console logs, debugger statements, placeholders, TODO markers, documentation, licensing, and unused dependencies

Understanding The Report

The report starts with an overall status, then groups findings by category.

  • READY: no errors or warnings were found
  • READY WITH WARNINGS: no blocking errors were found, but review is recommended
  • NOT READY: at least one blocking error needs to be fixed

Every finding includes:

  • What: the issue ShipIt detected
  • Where: the file, directory, or configuration area to inspect
  • Fix: the recommended next action

ShipIt exits with status 1 when errors are found, making it suitable for CI and deployment checks.

Development

npm install
npm run dev -- audit .
npm run build
npm start -- audit .

Static checks are intentionally conservative. Use browser testing, Lighthouse, axe, and your deployment platform's security tools for deeper validation.

License

ISC