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

@nodesource/ncm-proxy

v1.0.0

Published

Local Proxy for NCM 2.0

Downloads

5

Readme

ncm-proxy

Local Proxy for NCM 2.0.

About

This is a simple proxy server that is run locally on the computer doing the npm installations. When an install happens it will use the NCM API to look up score data and then either just log what was done or rewrite the proxied results to prevent installs of non-certified information.

Usage

Start an ncm proxy server on port 14313 (14=N, 3=C, 13=M):

$ NCM_TOKEN=xxx npx @nodesource/ncm-proxy

To obtain an ncm token please see the docs.

Then configure as your npm registry:

$ npm install express --registry=http://localhost:14313

Custom port

Set the PORT environment variable to launch on a different port:

$ NCM_TOKEN=xxx PORT=8080 npx @nodesource/ncm-proxy

Custom registry

You can also use a different registry than the default https://registry.npmjs.org/:

$ NCM_TOKEN=xxx npx @nodesource/ncm-proxy https://registry.npmjs.org

Routes

All except listed routes are simply proxied through:

GET /:package

GET /@scope%2f:package

Rewrite tarball urls to point at the proxy.

GET /:package/-/:package-:version.tgz

GET /@:scope?/:package/-/:package-:version.tgz

Return 404 if the module has a score lower than 85 or is on the whitelist, otherwise proxy through.

License & copyright

Copyright © NodeSource.

Licensed under the MIT open source license, see the LICENSE file for details.