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

solanatestforge

v0.1.0

Published

Test framework with forked state, security rules, and fuzzing for Solana/Anchor programs. Fork live devnet state, scan IDLs, hammer with 1000 random inputs — no deploys, no SOL.

Readme

solanatestforge

An engineer's toolkit for safer Anchor programs — fork live state, scan IDLs against security rules, and fuzz with boundary-aware inputs. All offline, no deploys, no SOL.

$ npm i -g solanatestforge
$ solforge --help

Commands

solforge fork <network> <programId>

Snapshot every account owned by a program from devnet or mainnet-beta. The JSON dump is reproducible state you can diff, replay, or load into tests.

solforge fork devnet ERSbyEx6s4MJnAem1vjmZW8Wv2cQdx1U4Fytuo6qy8ro
# -> .solforge/fork_<prog>_<slot>.json

solforge security <idl.json>

Static analysis over an Anchor IDL. Seven rules, severity-ranked:

| part | finds | severity | |-----------|------------------------------------------------------------|----------| | MIS-SIGN | authority-shaped accounts declared without Signer<'info> | critical | | UNCHK-OWN | UncheckedAccount used for owned state | critical | | ARITH-OVF | raw +/-/* on u64/u128 without checked_* | high | | REINIT | init on a mutable target without close/realloc | high | | CPI-AUTH | CPI calls signed by the wrong seed / user-controlled PDA | high | | RENT-EX | close = x without post-transfer lamport assertion | medium | | PDA-BUMP | non-canonical bump reused across instructions | medium |

solforge security ./target/idl/my_program.json

solforge fuzz <idl.json> [-n 1000]

Boundary-aware random input hammering. Generates u64::MAX, -1, 0, and random inputs against every instruction. Reports crashes, overflows, div-by-zero, and invariant breaks.

solforge fuzz ./target/idl/my_program.json --iterations 1000

solforge test

Run tests against a forked snapshot without a running validator.

solforge init

Scaffold a fresh test project with sensible defaults.

Why

anchor test runs your unit tests. bankrun and solana-test-validator run your program. Neither one inspects the program for a known vulnerability class, neither one fuzzes it against boundary inputs, and neither one will fork live state without a deploy. solforge does all three.

Requirements

  • Node.js 18+
  • No Rust toolchain required

License

MIT