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

docker-manifest

v2.0.1

Published

Get manifest info for a docker image.

Downloads

16

Readme

Installing

$ npm install docker-manifest

Usage

const const dockerManifest = require('docker-manifest');

dockerManifest.getImageManifest('library/alpine').then((manifest) => {
  console.log(manifest);
});

You can also provide configuration options as a second parameter to getImageManifest. This allows for the use of authentication on the registry and customization of how axios makes HTTPS requests.

Request Config

{
  // `auth` is used to provide authentication information if required for
  // the registry.  This is typically only for private registries and is
  // not required to get manifest info for public images in the Docker
  // Hub.
  auth: {
    username: 'foo',
    password: 'bar'
  },

  // `requestOptions` is passed directly to Axios when it makes HTTPS
  // requests to the registry.  This can be used to set any option allowed
  // by Axios, but params and headers will be overwritten.  Example use 
  // for this is to allow the use of self-signed certificates by passing 
  // a Certificate Authority to verify against. See https://github.com/axios/axios
  // for more info on options.
  requestOptions: {
    httpsAgent: new https.Agent({  // HTTPS Agent configured to use a self-signed cert
      ca: [ca],
      ecdhCurve: 'auto',
    }),
  }
}

Examples

Getting manifest info for the image 'library/alpine':

const dockerManifest = require('docker-manifest');

dockerManifest.getImageManifest('library/alpine').then((manifest) => {
  console.log(manifest);
});

Getting manifest info from a private registry with a self-signed certificate:

const dockerManifest = require('docker-manifest');

const image = 'private-registry.com/my-image';
const ca = fs.readFileSync('ca.pem');

const options = {
  auth: {
    username: 'foo',
    password: 'bar',
  },
  requestOptions: {
    httpsAgent: new https.Agent({
      ca: [ca],
      ecdhCurve: 'auto',  // needed for node >v8.5.0 if server uses elliptic curve
    }),
  },
};

dockerManifest.getImageManifest(image, options).then((manifest) => {
  console.log(manifest);
});