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

fixedcode

v0.2.2

Published

Spec-driven, deterministic code generation engine. Same spec → same code, every time.

Readme

fixedcode

The FixedCode CLI and programmatic API.

npm version License: Apache-2.0 Node

Spec-driven, deterministic code generation for the AI era. YAML in, production code out, same spec → same code every time.

Full project docs: https://github.com/gibbon/fixedcode

Install

npm install -g fixedcode
# or as a dev dep:
npm install --save-dev fixedcode

CLI

| Command | Description | |---|---| | fixedcode generate <spec.yaml> -o <out> | Generate code from a spec into <out>. | | fixedcode build <specDir> -o <out> | Generate from every spec in a directory; consolidates migrations. | | fixedcode verify <spec.yaml> <outputDir> | Verify every expected file exists. | | fixedcode deploy <buildDir> <targetDir> | Copy generated output into a target project. | | fixedcode validate <spec.yaml> | Validate a spec without generating. | | fixedcode draft <kind> "<description>" -o <out.yaml> | LLM-assisted spec drafting. | | fixedcode enrich <outputDir> | LLM-assisted extension-point fill-in. | | fixedcode registry list \| search \| install \| publish | Discover, install, publish bundles. | | fixedcode cfr catalog \| suggest \| check \| report | Cross-Functional Requirements tooling. | | fixedcode bundle init <name> | Scaffold a new bundle. |

Run fixedcode <command> --help for full options.

Quickstart

# install the CLI
npm install -g fixedcode

# install a bundle (registry-hosted)
fixedcode registry install spring-domain

# generate
fixedcode generate my-domain.yaml -o build
fixedcode verify my-domain.yaml build

# (optional) deploy into an existing project
fixedcode deploy build /path/to/your/project

Programmatic API

import {
  generate,
  validate,
  build,
  deploy,
  verify,
  fetchRegistry,
  searchRegistry,
  installPackage,
  publishPackage,
  renderTemplates,
} from 'fixedcode';

await generate({
  specPath: './my-domain.yaml',
  outputDir: './build',
});

Documentation

License

Apache-2.0