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

@appport/recipe

v0.1.1

Published

AppWorks business recipes: the appport.recipe/1 source model, validation, dependency locks and source packages. Executes nothing and grants no authority.

Readme

@appport/recipe

AppWorks business recipes: the appport.recipe/1 source model, a closed typed expression form, validation with structured findings, dependency locks (appport.recipe-lock/1) and source packages (appport.recipe-package/1). Specification: spec/recipe-1.md in rkendel1/appworks. JSON Schemas ship in schemas/.

| Area | Exports | |---|---| | Source | types, validateRecipe (source vs environment findings), validateRecipeInput, recipeDependencies | | Expressions | checkExpression, evaluateExpression | | Lock | createRecipeLock, checkRecipeLock, portableLock, substituteProvider | | Package | createRecipePackage, recipePackageDigest, serializeRecipePackage, loadRecipePackage, recipePackageIdentity, recipePackageBinding |

Depends only on the published @appport/protocol 1.3.0, @appport/schema 1.1.3 and @appport/integration 1.2.2, and uses their checks directly: lintIntegration for dependencies (canonical targets included), lintRule for rules, compareSchemas for interfaces. Canonical discovery, fulfillment evaluation, resolution and binding are AppPort's (@appport/core 1.4.0): resolve with it, then pass the resolvedDependency() records to createRecipeLock.

import { resolvedDependency } from "@appport/core";
import { createRecipeLock, checkRecipeLock, portableLock } from "@appport/recipe";

const lock = createRecipeLock(recipe, { contracts, resolutions: { "submit-invoice": resolvedDependency(result) } });
checkRecipeLock(lock, recipe, { contracts, providers });   // findings say: regenerate, revalidate or re-resolve
portableLock(lock);                                         // canonical identity only: what a package carries

A lock's canonical part (contract and capability digests) is portable; its resolution part (provider, registration, claim) belongs to one environment. A contract change requires revalidation; a provider change requires re-resolution; neither invalidates the recipe source. A lock grants no authority: binding still requires a grant for the provider's capability.

It executes nothing, selects no provider, grants no authority, and does not depend on Distribution Protocol or any registry. A source package is never executable. Not implemented: a compiler, a runtime, extraction and migration (repository assessment is @appport/assessment). Part of the AppPort ecosystem, not of the AppPort protocol.