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

@fdekit/catalog

v0.6.1

Published

Provider, connector, and recipe manifests: the shared source of truth for FDEKit scaffolding, docs, and deployment surfaces

Readme

@fdekit/catalog

@fdekit/catalog is the shared source of truth for FDEKit provider, connector, and recipe metadata. The CLI uses it for scaffolding and help; documentation generators and deployment surfaces can consume the same typed manifests without importing CLI internals.

import {
  connectorManifest,
  connectorNames,
  providerManifest,
  recipeManifests,
} from '@fdekit/catalog';

const github = connectorManifest('github');
const availableConnectors = connectorNames();
const openai = providerManifest('openai');

Canonical names and supported aliases resolve through providerManifest() and connectorManifest(). Use providerScaffold() or connectorScaffold() when generating configuration and dependency entries. Unknown lookups return undefined; requireRecipeManifest() throws for an unknown recipe.

The package is metadata, not a plugin loader or remote marketplace. Importing it does not load provider SDKs, connector credentials, or executable customer modules.

FDEKit packages are released as one fixed version group. Dependency helpers read this package's own version, with FDEKIT_SCAFFOLD_VERSION available for repository example synchronization and tests.