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

hmpo-node-standards

v3.0.0

Published

Cross-project node standards at HMPO

Readme

hmpo-node-standards

This hmpo-node-standards is a shared dependency that helps standardise code across HMPO services.

Installation

Add hmpo-node-standards to your project’s package.json. For example.

  "devDependencies": {
    "hmpo-node-standards": "^2.0.0"
  }

Usage

checkengines verifies if the current Node and npm version match the required version in package.json, if engineStrict is set to true.

checkgit prevents force pushes, deletions and uncommitted changes of protected branches.

comparelocales checks for missing translation keys between two locales (English and Welsh). Fails if any keys are missing.

commitmsg enforces proper commit message formatting by ensuring that each commit starts with either a JIRA ticket ID or an approved prefix. Valid commit prefixes include:

  • ABC-1234 Commit message.

  • CHORE: Commit message.

  • NOJIRA: Commit message.

  • WIP: Commit message.

lintapostrophes verifies correct apostrophe usage in files.

semver can be used to compare two semantic versions of your Node.js app. It checks whether the first version satisfies the constraint that is defined by the second version. For example:

  • Version 1.2.3 compared to ^1.2.0 passes, because ^1.2.0 allows any version from 1.2.0 up to (but not including) 2.0.0.
  • Version 1.2.3 compared to ^2.0.0 fails, because 1.2.3 is less than 2.0.0 which does not satisfy the constraint.

update-package add hmpo standard scripts to your package.json if dependencies are present.