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

@forge-kit-dev/core

v0.2.0

Published

Harness orchestrator, module loader, and conflict resolver for forge.

Downloads

43

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

padd_60padd_60

Keywords

Readme

@forge-kit-dev/core

The orchestration layer. Defines the Harness, the Module contract, the module loader, the rule conflict resolver, and file-path helpers for .forge/runs/<runId>/.

Design tenets

  1. Thin by construction. @forge-kit-dev/core has no host-specific code. The CLI brings in a runtime adapter (@forge-kit-dev/cli imports @forge-kit-dev/core plus the claude-code runtime in v0.1) and wires it into new Harness(...). That means:
    • core typechecks without Claude Code types in scope
    • tests instantiate Harnesses with a stub runtime
    • a v0.2 standalone adapter (Anthropic SDK) can be added without touching core
  2. Fail at construction, not at first run. The Harness validates active module presence and detects rule conflicts in its constructor. A misconfigured project should be unable to start a run.
  3. Determinism. loadModules() sorts by precedence, composePrompt() walks modules in load order and skills in declaration order. This is what makes forge test:meta-eval (Step 10) meaningful.

What's here vs what's in Step 9

Everything except Harness.run() is fully implemented in v0.1. run() is intentionally a throwing stub — the pipeline it will drive depends on @forge-kit-dev/agents + a concrete runtime, both of which ship in Step 9. The signature is already frozen so the CLI and modules can type-check against the full API.