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 🙏

© 2024 – Pkg Stats / Ryan Hefner

omegapm-require

v0.0.5

Published

require a specific hash of a node package

Downloads

2

Readme

omegapm-require

Ωpm (omega package manager) replacement for node.js require

Concept

At the top of a node.js script, you usually require module internals like this:

imp = require("important-package");
cry = require("crypto-package");
loc = require("./local/path");

Use omegapm-require to verify that your modules are unchanged before requiring them:

Ω = require("omegapm-require");
Ω("important-package", "HASH", function(err, imp) {
  Ω("crypto-package", "HASH", function(err, cry) {
    // doesn't support local files yet
    loc = require("./local/path");

    // you have access to all of the modules in this scope
  });
});

Getting the hash of a module

The hash of a module is not the same as the git commit SHA. The commit SHA is actually influenced by the commit message, timestamp, and author. The purpose of this SHA check is not to check the commit action, but that this module matches the build intended by the module developer and its implementer, and it remains unchanged.

Once you install this package, you can get its hash:

npm install omegapm-require -g
cd top/directory/of/node/server
npm install PACKAGE_NAME
omegapm-hash PACKAGE_NAME
> hashhashhashash

License

GPLv3+