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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@containerbase/base

v14.31.1

Published

Metadata about the tools supported by containerbase

Downloads

80,241

Readme

@containerbase/base

Metadata about the tools that Containerbase supports.

The data is generated from the Containerbase sources and released with the same version as Containerbase itself. This allows a consumer of this library to determine which tools can be used with a given version of Containerbase (via /usr/local/containerbase/version): if the image has the same major version as this package and a version greater than or equal to the package version, every tool listed here can be installed in that image. A new major version may remove tools, so compare against the package of the image's major version.

The package version to compare with is exported too:

import pkg from '@containerbase/base/package.json' with { type: 'json' };

pkg.version; // eg. '14.2.0'

Usage

import { toolNames, tools, type ToolName } from '@containerbase/base';

tools.composer; // { parent: 'php' }
tools.kas; // { type: 'pip', parent: 'python' }

function install(tool: ToolName): void {
  // `ToolName` is a union of all supported names
}

The raw data and its json schema are also exported, for consumers which don't use TypeScript:

import tools from '@containerbase/base/tools.json' with { type: 'json' };

The zod schemas live behind a separate entry point, so the default export stays dependency free:

import { SupportedTools, ToolName } from '@containerbase/base/zod';

Contents

Each entry may carry the following metadata:

| Field | Description | | ------------ | --------------------------------------------------------------------------------------------------------------- | | type | the installer used for the tool, one of gem, npm or pip | | parent | the tool it depends on, eg. composer depends on php, which requires php to be installed before composer | | deprecated | the tool should not be used any more | | root | the tool can only be installed as root, so at image build time |

Only the names install-tool accepts are listed. Packages installed with an arbitrary name via install-gem, install-npm or install-pip are not, as that list is unbounded.

Development

The files in data/ and src/data.ts are generated, run pnpm tools in the repository root to update them.