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

@cardano-slips/flow

v0.0.3

Published

The client side of Cardano Slips: CIP-30 orchestration, local balancing, and the React components that render a Slip and block a signature when its effects disagree

Readme

@cardano-slips/flow

The client side. It resolves a Slip link, renders it, connects a wallet, balances the transaction against the person's own UTxOs, derives what that transaction actually does, and refuses to ask for a signature when the answer disagrees with what the endpoint declared.

pnpm add @cardano-slips/flow react

What it does

| Step | What happens | | --- | --- | | resolve | the shared link through slips.json, then GET for the Slip's metadata | | render | the card, the parameter form generated from what the endpoint declared, and the wallet selector | | build | POST for the publisher's side of the transaction | | balance | locally, against the wallet's own UTxOs — the endpoint never sees them | | derive | what the built transaction does, from its bytes | | compare | against the intent, and block on any disagreement | | sign | signTx → assemble the witness set into the body → submitTx |

useSlip, useWallet and useEffects are the composable surface for anyone who wants the machinery without our components.

It refuses; it does not decide

The comparison is verifier's, and it is a pure function so the attack examples run the same code path a real signature does. This package is the consequence of a verdict: a mismatch renders as a block with no control to press. There is no override to configure — not a setting, not an allowlist, not a confirmation. See Blocking.

It does not own the page

These components are meant to be dropped into someone else's page. No fixed positioning, no assumption about the document, and styles that survive an inherited font stack. tokens.css holds the design tokens as CSS custom properties and is the only place a colour is defined.

React is a peer dependency: your copy is the one that renders, and a second copy in the tree is the oldest breakage in the ecosystem.

Entry point

One export, the package root. Deep imports into dist/ are not a supported surface, so moving a file is never a breaking change:

import { ... } from "@cardano-slips/flow"

MIT licensed. Issues and contribution guide: cardano-slips.