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

@eco-dev/core

v0.0.1-alpha.1

Published

Project Eco shared contracts, identity primitives, and event envelope.

Downloads

28

Readme

@eco-dev/core

Project Eco shared contract seed.

This package currently promotes only the minimal EcoEventEnvelope contract that passed the first bounded Forge/DGX/Mac integration gate.

@eco-dev/core controls Eco protocol compatibility. Customers and partners define their own domain contracts on top of it, but they do not redefine the Eco protocol namespace.

Promotion Evidence

  • Forge adapter gate: G:/eco-artifacts/eco-lineage/forge-infra-002/gate-result-v2.json
  • DGX reducer gate: G:/eco-artifacts/eco-lineage/dgx-state-002/gate-result-v1.json
  • Mac observation gate: G:/eco-artifacts/eco-lineage/mac-reactive-002/gate-result-v1.json
  • Unified integration: G:/eco-artifacts/eco-lineage/unified-integration-001/unified-integration-report.json

Scope

Promoted now:

  • canonical JSON helper
  • SHA-256 helper
  • EcoEventEnvelope
  • protocol/domain boundary helpers
  • EcoDomainContract
  • Zod schemas for runtime validation and inferred TypeScript types
  • envelope validation
  • duplicate (source_id, source_seq) detection
  • source sequence gap detection

Not promoted yet:

  • Forge infra adapter implementation
  • DGX reducer implementation
  • Mac reactive adapter implementation
  • runtime WAL/replay storage
  • UI/chat/fork workflow
  • customer-specific domain schemas

Those remain patch-draft evidence until the canonical package layout is chosen.

Protocol Boundary

Eco protocol contracts are strict and conformance-tested. They are the rails that keep plugins, partners, agents, and runtimes compatible.

Customer/domain contracts are flexible and namespaced. They extend the protocol and describe customer-specific workflows, entities, policies, and plugin payloads.

Rule:

Eco controls the rails.
Users control what runs on the rails.

See docs/protocol-boundary.md.

TypeScript-First Validation

@eco-dev/core exports Zod schemas so Nuxt/Nitro apps, ingestion pipelines, RAG tooling, adapters, plugins, and tests share the same runtime validation boundary.

Use these instead of inventing package-local validators:

  • EcoEventEnvelopeSchema
  • EcoDomainContractSchema
  • EcoCompatibilityProfileSchema

Gate

npm install
npm run gate