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

@voxel51/voodo

v0.0.5

Published

Voxel51's official design ontology (VOODO) system

Readme

VOODO: Voxel's Official Design Ontology

This library acts as both a design system and a component library for Voxel51's front-end applications.

Note: this library is currently in a pre-release state and may have frequent breaking changes. This library will adhere to semantic versioning best-practices starting with version 1.0.0.

Installation

npm i @voxel51/voodo

Usage

Using components

This library exports a number of React components which are consistent with VOODO's look and feel.

import { Button } from "@voxel51/voodo";

export const Component = () => {
    return (
        <Button onClick={() => alert("Button clicked!")}>
            Click me!
        </Button>
    )
};

Note that you'll need to import this library's theme somewhere in your application for the components to be styled correctly. See CSS Themes.

Theming

CSS Themes

This library is based on Tailwind and exports a set of CSS variables which capture the relevant colors, spacing, typography, etc.

To consume the CSS variables, simply include the following line somewhere in your application.

import "@voxel51/voodo/theme.css";

Usage with MUI

This library also exports theme configuration (in the form of a Material ThemeConfig) which can be used to generate an MUI theme.


import { createTheme, ThemeProvider } from '@mui/material/styles';
import { defaultMUIThemeConfig, createMUIThemeConfig } from '@voxel51/voodo';

// Option 1: Use default (dark mode)
const theme = createTheme(defaultMUIThemeConfig);

// Option 2: Create light mode
const lightTheme = createTheme(createMUIThemeConfig({ mode: 'light' }));

// Option 3: With overrides
const customTheme = createTheme(
    createMUIThemeConfig({
        mode: 'dark',
        overrides: {
            palette: {
                primary: { main: '#custom-color' },
            },
        },
    })
);

function App() {
    return (
        <ThemeProvider theme={theme}>
            {/* Your app */}
        </ThemeProvider>
    );
}

Contributing

This library is based on HeadlessUI and Tailwind. Components should be minimal, intentional, and adhere strictly to the Voxel51's internal design guidelines.

General rules of thumb:

  • Prefer explicit behavior over implicit
  • Provide configurability where appropriate
    • Ensure top-level properties adhere to design guidelines
    • Allow for property overrides
  • Prefer small, composable components

Publishing

This library is published to NPM via GitHub Actions workflows. Releases are triggered by tagging a commit with a v<version> tag, where <version> should match the version property in package.json. For example, the initial release has the tag v0.0.1.

Once a release is tagged and published, the version property in package.json should receive a patch bump.

This library is currently in a pre-release state, with versions matching 0.x.y. Standard semantic versioning will be enforced starting with version 1.0.0.