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

@zixcel/projection-client

v0.10.5

Published

Bounded renderer-independent projection adoption and presentation runtime

Readme

@zixcel/projection-client

日本語

Adopt a validated display snapshot and keep updates tied to the correct revision.

What you can do

  • Reject stale or mismatched snapshots.
  • Track navigation and interaction state across accepted updates.

Current scope

The host supplies transport and trusted rendering. The client does not invent actions or canonical application state.

Use the version declared by this source and verify the official registry artifact/provenance before adopting a new release.

Getting started

Dependencies use exact public npm versions. The repository workspace links the current source for development; owner CI separately installs the packed archives outside this checkout. No private registry or excluded local archive is required.

Use the package manager matching the checked-in lockfile and the Node.js version declared in package.json or the development configuration. Run from this repository:

pnpm install --frozen-lockfile
pnpm test

Documentation and source

Usage guide

Implementation and public interfaces · Verification cases · Contributing · Security reporting · License · Attribution notices

Release provenance

Current releases use GitHub Actions OIDC trusted publishing from zixcel/data-presentation (publish-npm.yml), without a stored npm publishing token. The workflow verifies reviewed archive hashes and requires npm provenance metadata. Check the published version on npm and verify registry signatures and provenance with npm audit signatures in an installed consumer project. Package runtime behavior and API contracts are unchanged by this release.