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

@infrix/widgets

v0.1.0

Published

Embed Infrix proof verification, receipts, Cinema replay, task cards, and trust-boundary explanations in your app — verified in-browser, with no node trust by default.

Readme

@infrix/widgets

Embed Infrix proof verification, receipts, Cinema replay, task cards, and trust-boundary explanations in your app — verified in-browser, with no node trust by default.

npm install @infrix/widgets
import {
  InfrixProofReceipt,
  InfrixVerifyButton,
  InfrixCinemaReplay,
  InfrixTrustBoundary,
  InfrixProofStory,
  InfrixTaskCard,
  InfrixErrorResolution,
} from '@infrix/widgets';

<InfrixProofReceipt bundle={bundle} />
<InfrixVerifyButton bundleUrl="/proof.infrix.json" onVerify={(r) => console.log(r.status)} />
<InfrixCinemaReplay story={story} />
<InfrixTrustBoundary receipt={receipt} />

react and react-dom (>= 18) are peer dependencies. A framework-neutral Web Component build lives in @infrix/widgets-webcomponent.

Honest by construction

  • Verification runs in the browser. Nothing is sent anywhere unless you explicitly pass an l0 verification endpoint — by default no proof payload leaves the page.
  • An offline verdict is never inflated to L4. Reaching L4 requires confirming the L0 anchor; without it the widget says "Locally verified. Live L0 not checked." and never "Fully verified."
  • No green badge unless it was earned. Assurance badges are data-gated by the same canonical UX label fixture Nexus and the SDK use — a failed verification, or an operator-attested-only state, shows no positive badge.
  • No node trust. Every receipt is built with nodeTrusted: false.

Every component supports

theme (light | dark | auto), variant (full | compact), mobile layout, accessibility labels, onVerify, onError, and no external telemetry. Styles are injected once under a scoped .iw-widget root (every class is iw--prefixed) so they cannot collide with — or be broken by — your app's CSS. You can instead link the stylesheet:

import '@infrix/widgets/styles.css';

Live L0 verification

By default the widgets verify the offline cryptographic structure. To confirm the L0 anchor live, pass l0 — a verification-backend URL you control (e.g. an infrix verify service). The bundle is POSTed to it ONLY then:

<InfrixProofReceipt bundle={bundle} l0="https://verify.example/l0" />

The endpoint must return { "l0Verified": boolean, "network"?: string }.

The verifier core

The framework-neutral verifier is exported for non-React use:

import { verifyBundle, verifyStory, verifyReceiptResult } from '@infrix/widgets/verifier';
const result = await verifyStory(shareBundle);
console.log(result.honestLabel); // "Locally verified. Live L0 not checked."