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

@0xhoneyjar/beacon-schema

v0.1.0

Published

Sealed Effect Schema for the Freeside MCP federation beacon contract. Cycle C base · Cycle D extends with docs.* additively.

Readme

@0xhoneyjar/beacon-schema

Sealed Effect Schema for the Freeside MCP federation beacon contract. Workspace package inside freeside-mcp-gateway/packages/beacon-schema/.

Cycle C v0.3 broadcast layer · base shape (schema_version: "2"). Cycle D extends the docs.* block additively (no breaking change · v0.2.0 bump).

Disambiguation

Two names look similar — they are not the same thing.

| Name | What | Where | Audience | |---|---|---|---| | construct-beacon | Construct in the constructs-network registry · ships SKILLS for AI-content-readability + MCP-codegen authoring (auditing-content, defining-mcp-tools, generating-markdown, accepting-payments) | constructs.network | Authors writing a beacon.yaml for their MCP construct | | @0xhoneyjar/beacon-schema | npm package · sealed Effect Schema for BeaconV2Schema runtime validation + JSON Schema export + build-beacon-json CLI | npm registry · gateway monorepo | Gateway implementation + construct build steps + future external integrators |

Read it as: construct-beacon HELPS YOU AUTHOR a beacon.yaml; @0xhoneyjar/beacon-schema VALIDATES that your beacon.yaml conforms to the federation contract.

Install

pnpm add -D @0xhoneyjar/beacon-schema
# requires effect ^3.10.0 as peerDep

Use · validate a beacon at runtime

import { BeaconV2Schema, decodeBeacon } from "@0xhoneyjar/beacon-schema";
import { Effect } from "effect";

const result = await Effect.runPromise(
  decodeBeacon(JSON.parse(rawBeaconJson))
);
// result is a typed BeaconV2 · throws on invalid input

Use · YAML→JSON adapter (build step)

npx build-beacon-json --in beacon.yaml --out app/.well-known/beacon.json

Wired into each construct's package.json:

{
  "scripts": {
    "build:beacon": "build-beacon-json --in beacon.yaml --out app/.well-known/beacon.json"
  }
}

Exit codes:

| Code | Meaning | |---|---| | 0 | Validation passed · JSON written | | 1 | Validation failed · ParseError on stderr | | 2 | Usage error (missing --in / --out) |

Use · JSON Schema export

import { BeaconV2JsonSchema } from "@0xhoneyjar/beacon-schema";
// canonical JSON Schema · publish at /.well-known/beacon-schema/v2.json

Schema shape (v2)

# beacon.yaml v2 · minimal
schema_version: "2"
mcp:
  shape: data | tool | proxy
  paths: [stdio, remote-http]
  remote: { transport: streamable-http, endpoint: ... }    # required if paths includes remote-http
  auth: { kind: none | api-key, header?, credentials_ref? }
  capabilities: [tools, resources, prompts, sampling, logging]
  tools: [...]
  pricing: { model: free | per-call | subscription | pay-per-call, description }
  publisher: <org>

Auth refine rules

| auth.kind | header | credentials_ref | |---|---|---| | none | MUST be omitted | MUST be omitted | | api-key | REQUIRED | REQUIRED | | jwt, oauth | reserved · v0.3 schema accepts but gateway throws CredentialResolverNotImplemented at boot |

credentials_ref.key convention

SCREAMING_SNAKE_CASE only (Railway env-var pattern · max 128 chars).

docs: block

Cycle C ships docs: Schema.optional(Schema.Unknown) — accepts any docs payload during the transition. Cycle D files an additive PR replacing Schema.Unknown with a concrete DocsBlockSchema (tagline + example_invocations + assets + changelog_url). See Cycle D coordination contract.

Develop

pnpm install        # from repo root · workspace setup
pnpm typecheck      # tsc --noEmit
pnpm build          # tsc -b → dist/
pnpm test           # tsx --test tests/*.test.ts (14 tests)

Versioning

| Version | Cycle | Change | |---|---|---| | 0.1.0 | Cycle C v0.3 (this) | Base BeaconV2Schema · mcp + cli + payment + auth + credentials_ref · docs:Schema.Unknown placeholder | | 0.2.0 | Cycle D (planned · additive PR) | Replaces docs: Schema.Unknown with DocsBlockSchema (tagline + example_invocations + assets + changelog_url) | | 1.0.0 | After v0.3 stable | Promote to 1.0 once schema is exercised by 3+ tenants in production |

License

MIT