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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pem-parser

v0.0.1

Published

SSL CA Cert file parsing library.

Downloads

126

Readme

pem-parser

Breaks apart CA Certificate files that contain multiple PEMs into an array of PEMs. This is useful when you are passing CA Certificate files which contains multiple PEMs into tls.connect.

The TLS documentation indicates that the ca option can be either a string containing a single PEM or an array of strings, each containing its own PEM.

Install

$ npm install pem-parser

Usage

var PEMParser = require('pem-parser');
var caCerts = PEMParser.loadCACertsFromFile(caCertFilename); // The file named caCertFilename can contain multiple PEMs.
var socket = require('tls').connect(this.port, this.host, {
  key:  fs.readFileSync(keyFile),
  cert: fs.readFileSync(certFile),
  ca: caCerts
}, function(){
  console.log('Connected!');
});

// or alternatively, you can do:
var fileContents = fs.readFileSync(caCertFilename).toString();
var caCerts = PEMParser.loadCACerts(fileContents);

Setup

First, install the development dependencies:

$ npm install

Then, try running the tests:

$ npm test

Pull Requests

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Make sure the tests pass by calling npm test.
  5. Make sure the linter passes by calling npm run-script lint.
  6. Push to the branch (git push origin my-new-feature)
  7. Create new Pull Request

Any contributors to the master pem-parser repository must sign the Individual Contributor License Agreement (CLA). It's a short form that covers our bases and makes sure you're eligible to contribute.

When you have a change you'd like to see in the master repository, send a pull request. Before we merge your request, we'll make sure you're in the list of people who have signed a CLA.