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

flatland-client

v0.1.4

Published

Flatland client — the durable client for the hosted Flatland engine. Your model is a file you own (~/.flatland/models/*.flatland.json), versioned in your own git; the server is a pure function that holds nothing at rest. Includes a local MCP stdio bridge

Readme

The durable client for the hosted Flatland engine, and a local MCP bridge for Claude Code / Cursor.

Your model lives at ~/.flatland/models/<name>.flatland.json on your machine — versioned in your own git, diffable, re-runnable anywhere. The hosted server is a pure function (/api/v2/*): the client ships the model IR in, the server computes/transforms and returns, and retains nothing at rest.

The MCP bridge (Claude Code / Cursor)

flatland-client mcp runs a local MCP stdio server. It holds the model IR on your machine (durable across sessions) and routes compute to the hosted engine (metered). The usual way to wire it is:

npx flatland-setup fl_live_YOUR_KEY    # configures `flatland-client mcp` by default

Or by hand, in your MCP client config:

{ "mcpServers": { "flatland": { "command": "npx", "args": ["-y", "flatland-client", "mcp"] } } }

The key is read from ~/.flatland/config.json (written by flatland-setup) or the FLATLAND_API_KEY env var — it is never embedded in the MCP config.

As a library

import { create, load, httpTransport } from "flatland-client";

const t = httpTransport({ apiKey: "fl_live_..." });
const h = await create("acme_plan", t);             // writes ~/.flatland/models/acme_plan.flatland.json
await h.bulkAdd([
  { name: "revenue", type: "Currency", value: 1000 },
  { name: "cost", type: "Currency", value: 400 },
  { name: "profit", type: "Currency", formula: "revenue - cost" },
]);
console.log((await h.compile()).values.profit.value);  // metered compute, nothing stored server-side

// new session / a machine that has the file:
const h2 = await load("acme_plan", t);                 // durable across restart

CLI

flatland-client mcp              # run the local MCP stdio server
flatland-client list            # list durable models on this machine
flatland-client create <name>   # create a model, persisted locally
flatland-client compile <name>  # compile a local model via the hosted engine

Durability + safety contract

  • Atomic writes (tmp + rename) — a crash never leaves a half-written model.
  • Fail-loud (F2) — a failed mutation (5xx, or a rejected 4xx) raises and leaves the local file untouched; a failure is never a silent stale-file "success".
  • No server fallbackload() of a missing file raises; the server never held your model.
  • Envelope versioning{ "flatland_ir_version": 1, "ir": {...} }; a too-new envelope is refused before it is persisted.
  • Path-traversal-safe model names; the API key goes only in the X-API-Key header — never logged.

Get a key at https://flatlandfi.com/install.

License

MIT. Covers the client only — the Flatland engine and API are a separate, proprietary service accessed with a paid API key.