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

@nash-script/cli

v0.4.0

Published

The Nash programming language

Readme

nash

A purely functional language with Elm/Haskell syntax that compiles to Untyped Plutus Core. Successor to Aiken: type classes, higher-kinded types, explicit Big (Data) vs little (native UPLC) representation types, macros, compile-time evaluation, property-based tests.

Taste

validator module Vesting exposing (main)

type Datum = Datum { owner : Bytes, deadline : Int }

@derive(Eq, Show, ToData, FromData)
type Redeemer = Claim | Cancel

main : Datum -> Redeemer -> Data -> unit
main datum redeemer ctx =
    case redeemer of
        Claim -> assert (lower datum.deadline < currentSlot ctx)
        Cancel -> assert (signedBy ctx datum.owner)

tests
    import Fuzz exposing (int)

    prop "deadline is never negative" =
        let d via int in
        do
            assert (lift d >= lift 0)

Development

cargo fmt --all
cargo clippy --all-targets --all-features -- -D warnings
cargo insta test

Changesets

We use sampo for versioning and releases. When you make a notable change, add a changeset:

sampo add

Only list crates you actually changed; sampo bumps dependents.

Release flow

  1. Push to main with a changeset file
  2. Sampo CI creates/updates a release PR that bumps versions and generates changelogs
  3. Merge the release PR
  4. Sampo publishes crates to crates.io and pushes version tags
  5. Tags trigger cargo-dist to build and publish:
    • GitHub Releases with platform binaries
    • Homebrew formula (brew install orbistry/tap/nash)
    • npm package (npx @nash-script/cli)