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

tls-test

v0.0.1

Published

A package to test TLS 1.2 compliance with your package manager

Downloads

837

Readme

TLS 1.2 for npmjs.com

The public npm registry (npmjs.com) is deprecating insecure versions of HTTPS and you will be required to use TLS 1.2 (or better) to download packages. Most versions of npm and Node.js are ready for this change but you can test your client by running:

npm install -g https://tls-test.npmjs.com/tls-test-1.0.0.tgz

This will install a test package over an HTTPS connection that already enforces TLS 1.2, instead of going to the public npm registry (which does not yet).

If this command succeeds, it will print the following message:

Hello! The tls-test package was successfully downloaded and installed.

Congratulations! Your package manager appears to support TLS 1.2.

If you do not see this message, then there was a problem downloading the package. You should ensure that you are running a currently supported version of Node.js and install the latest version of npm.

For more information, please see the npm documentation and if you have questions, check out the Software Development board of the GitHub Community forums.