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

create-flarekit-app

v0.2.0

Published

Start a Flare project — a headless script, a React app, an AI agent, or an MCP server, wired to a real network and pinned to the kit version it was generated against.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

blockchainoracleblockchainoracle

Keywords

flarecoston2createscaffoldstarterfassetsftsoweb3

Readme

create-flarekit-app

npm license

Start a Flare project.

Community-built. Not an official Flare Networks product.

Use it

npm create flarekit-app@latest my-app -- --template script
cd my-app && npm install && npm start

Templates

| --template | What you get | | --- | --- | | script | A Node script reading live FTSO prices. No wallet, no key. | | agent | An agent over the Vercel AI SDK with the Flare tools wired in. | | mcp | Your own MCP server serving the Flare tools to an agent host. |

Two more are named in the specification and not generated yet, rather than shipped unverified: react (needs a bundler, connector and provider tree run end to end) and widget (there is no embeddable widget package). Asking for either tells you so, with the reason.

Generated projects run live

This is the split worth knowing, and every generated README repeats it:

  • The documentation at flare-kit.xyz runs against the mock, so examples finish in seconds and need nothing configured.
  • Your generated project runs live against Coston2 testnet. The numbers change between runs because the protocol does.

Mock mode stays available from @flarekit-dev/core, and it is always labelled — never a fallback that appears when something fails.

Pinned, not floating

Generated projects pin the kit version the scaffolder was published against, so a project generated today still builds next month. It will not resolve whatever latest happens to mean on the day you run it.

It will not overwrite your work

The target directory must be empty. A directory holding only .git counts as empty, because that is how people start; anything else is refused by name before a single file is written.

Licence

MIT