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

@vinumcms/core

v0.20.0

Published

Pure content schemas, sanitizers and registries. No I/O, no React.

Downloads

7,439

Readme

@vinumcms/core

Pure schemas, sanitizers and registries. No I/O, no React, no imports from other Vinum packages — everything here is a pure function or a type, which is what makes it cheap to test and safe to import anywhere.

import { CORE_BLOCKS, createBlockRegistry, sanitizeBlocks, safeHref, isLive } from "@vinumcms/core";

const registry = createBlockRegistry(CORE_BLOCKS);
const blocks = sanitizeBlocks(untrustedJson, registry);  // unknown types dropped

What's here: the Page, Block, FormField, PageType and NavConfig models · every sanitize* function · the block registry · safeHref/safeSrc · isLive and the scheduling helpers · buildMeta and JSON-LD builders · the Store, MediaStore and Mailer interfaces.

Forms are one flat array of fields. Layout (width), structure (section, divider, pageBreak), conditions and validation rules are all properties of a field rather than containers around it, which is why a form stored before any of them existed still fits the type. fieldRows() packs fields into rows, visibleFields() resolves conditions, formPages() splits on page breaks and validateSubmission() decides — the browser and the server call the same four, so they cannot disagree. isInputField() is what keeps a section heading out of a submission. The builder and the full field reference are documented under Forms in @vinumcms/admin.

This package is the trust boundary. Anything arriving from an editor, a form post or an import file passes through a sanitizer here before it is stored or rendered.

Setup and theming live in @vinumcms/admin, which carries the getting-started guide for all of Vinum.