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

@tetsuo-ai/store-core

v0.1.0

Published

Shared config schema, SEO helpers, page sections, and the local sandbox bootstrap consumed by every AgenC store template (PLAN_2 Part C).

Downloads

87

Readme

@tetsuo-ai/store-core

The shared package every AgenC store template consumes (PLAN_2 Part C). All protocol/hire logic lives here and in @tetsuo-ai/marketplace-react; template code is layout + config ONLY. That architecture rule is what makes an instance update a dependency bump + redeploy (PLAN_2 C7), never a template-code merge — so keep new protocol logic here, not in templates.

Public surface

Each area is also a tree-shakeable subpath export.

config — the single configuration surface (C2)

import { defineStore } from "@tetsuo-ai/store-core";

export default defineStore({
  name: "Acme Agent Store",
  description: "Hire vetted agents for code review.",
  network: "localnet", // "localnet" | "devnet" | "mainnet"
  api: { baseUrl: "https://indexer.example.com" },
  referrer: { wallet: "<base58>", feeBps: 250 },
  branding: { poweredBy: true },
  seo: { siteUrl: "https://store.example.com" },
});
  • defineStore(config) / safeDefineStore(config) — validate + normalize. A misconfig throws StoreConfigError whose message lists every problem with its field path. Build-time validation:
    • referrer.wallet MUST be base58 (a wrong wallet would silently drop the owner's fees → hard error);
    • referrer.feeBps is range-checked against the combined cap REFERRER_COMBINED_FEE_BPS_CAP (protocol + operator + referrer ≤ 4000 bps);
    • network: "mainnet" fails until Phase 9 unless allowMainnet: true;
    • reserved payment flags (embedded/fiat/x402) fail closed until wired.
  • getDeployedSurface(config, probe) / SurfaceNotDeployedError — render an explicit "listings not live yet" page instead of an empty grid.
  • checkCombinedFee(...) — per-listing combined-fee pre-check so the checkout surfaces a clear error BEFORE building a transaction that would revert.
  • applyCuration(...) / curationToListingsFilter(...) — curation logic.

seo — the SEO surface (C3)

listingJsonLd / storeJsonLd (schema.org Service/Offer), storeMetadata / listingMetadata (OG/canonical), buildSitemapEntries / renderSitemapXml / buildRobotsTxt, listingAgentCard / buildLlmsTxt, and storeSeoContext.

sections — the shared page components (C3)

StoreShell, CatalogSection, ListingDetailSection, DashboardTaskSection, EarningsSection (the owner /earnings view), TrustSection, and the specced empty/error states (SurfaceNotDeployedSection, EmptyCatalogSection, ZeroMatchSection, IndexerUnreachableSection). Each wraps marketplace-react, so all three templates differ only in routing + curation.

upgrade — instance-upgrade primitives (C7)

checkStaleness, useChangelogFeed, and <UpdateBanner> (owner-visible; security updates flagged).

@tetsuo-ai/store-core/sandbox-up

The committed deterministic local-validator bootstrap. It reuses the agenc-protocol localnet stack (set AGENC_PROTOCOL_DIR, or place agenc-protocol as a workspace sibling) so template CI runs against exactly the on-chain state the protocol + SDK are tested against.

node scripts/sandbox-up.mjs up    # boot + init + seed (idempotent)
node scripts/sandbox-up.mjs env   # print the resolved sandbox env JSON
node scripts/sandbox-up.mjs down  # stop the validator

The P6.2 referrer gate

Referrer config is validated + stored + disclosed, but never injected and never fabricated as earnings. marketplace-react's resolveReferrerCapability() returns { live: false } until the on-chain referrer settlement leg (PLAN.md P6.2) ships; EarningsSection renders that not-live state honestly.

License

MIT