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

@websitekit/sdk

v0.1.1

Published

Issuance and settlement layer for tokenized page inventory — reads, writes and pricing for SlotSite.

Readme

@websitekit/sdk

Reads, writes and pricing for websitekit — an issuance and settlement layer for tokenized page inventory. A publisher marks regions of their page as slots; anyone buys one and becomes its effective owner, able to write its content, trade it as an ERC-721, or rent it to an advertiser.

npm install @websitekit/sdk viem

viem is a peer dependency: this package takes your client, so there is one copy of viem and one set of types.

Reading a board

Every read goes through SlotReader, a deliberately replaceable deployment — so reads take a SiteRef ({ site, reader }) rather than a bare address.

import { createPublicClient, http } from 'viem';
import { readSlots, readSiteTerms, ROBINHOOD_TESTNET, DEMO_SITE } from '@websitekit/sdk';

const client = createPublicClient({ chain, transport: http() });
const ref = { site: DEMO_SITE, reader: ROBINHOOD_TESTNET.reader! };

const terms = await readSiteTerms(client, ref);
const slots = await readSlots(client, ref, ['hero.headline', 'hero.image']);

Each slot carries what a page needs to render and what a buyer needs to decide: charged (what this buyer pays — the floor on a claim, the take price on a take), unaccruedRent and netCost for an encumbered position, and isAvailable for the publisher's listing toggle.

Buying

Never assemble a buy by hand. readBuyContext pins the quote, the encumbrance hash and the chain's clock to one block, and buildBuyFrom builds from exactly that:

import { readBuyContext, buildBuyFrom } from '@websitekit/sdk';

const context = await readBuyContext(client, ref, 'hero.headline');
const request = buildBuyFrom(ref.site, context, terms.settlementToken);
await walletClient.writeContract(request);

This SDK never holds a key. Every build* returns a request object your wallet layer sends.

Three rules worth knowing up front

  • settlementToken is required on every builder that moves money. There is no default: a native-shaped call against a token site reverts, and the same call is correct on a native site — so a default is silently right half the time.
  • Never parseEther a floor. minFloor derives from the settlement token's decimals, so 18 is wrong by 1e12 against 6-decimal USDG. Use parseFloor(amount, decimals).
  • Deadlines and liveness use block.timestamp, not Date.now(). The helpers here read the chain's clock for you; wall-clock answers are confidently wrong on a lagging L2.

Status

Testnet only, unaudited, and the contracts are not upgradeable — a site is a clone frozen to the implementation it was created from. Experimental software.

MIT © websitekit