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

@helyx/module-manifest

v0.14.0

Published

Validated manifests and dependency ordering for Helyx modules.

Readme

@helyx/module-manifest

Schemas, parsing and deterministic dependency ordering for Helyx module manifests and dashboard contributions.

Requirements

  • Node.js 24–26
  • npm 11 or newer

Use parseModuleManifest at trust boundaries. Invalid identifiers, versions, release stages, dependencies, settings, privacy declarations or dashboard actions are rejected before module execution. Every manifest must declare releaseStatus as planned, testing, beta or live.

Current manifest policy: v0.5

New Helyx modules use manifest v0.5. It retains the v0.4 privacy, classification and deployment policy and adds reviewed feature-level access, feature-scoped Discord capabilities and adapter risk, commandless permission operations, explicit settings mutation authority, range inputs, bounded managed-resource import, generic settings previews and managed-resource support visibility. An optional validated featureId associates individual settings, previews and managed-resource controls with a feature declared by that same v0.5 manifest.

The deployment policy remains:

  • deploymentSupport: hosted, self-hosted or both;
  • credentialRisk: none, low, medium, high or very-high;
  • deploymentReason: an internal, non-secret explanation of at most 300 characters; and
  • the v0.3 module classification fields (moduleKind, customerSelectable, countsAsInstalledModule and healthExposure).

Data-holding modules list their bounded collections and subject fields; no-data modules explicitly declare containsPersonalData: false. Parsers keep accepting v0.1 through v0.4 for compatibility; older versions do not gain or imply v0.5 feature, permission or disclosure authority. New manifests must use v0.5 and register a matching executable privacy provider through the SDK, including a zero-record provider when no personal data is held. The bot loader checks provider identity, version and declaration parity. The module-authoring guides bundled in @helyx/bot/documentation/ explain build, test and packaging requirements; exported schemas are the runtime validation contract.

Publication status

Published as a public scoped package under the Helyx Source Available Licence. Read the packaged LICENSE before installing, using, modifying, or distributing the software.