npm says published.
Flora proves it's out.

A publish can succeed while nobody can install it yet: the public listing lags, the wrong version goes out, or the files aren't the ones you built. Flora checks the public registry and the file npm actually serves, byte for byte, against what you packed.

PUBLISHED: @you/tool@1.2.0 is listed, and the file npm serves matches
what you packed, byte for byte.
NOT PUBLISHED: @you/tool isn't on npm's public list yet.
Nobody can install it.

How it works

  1. Pack. Flora reads your package's fingerprint from npm pack. npm packs the same files the same way every time.
  2. Publish the way you always do.
  3. Prove. Flora reads the public registry and fetches the published file. Only an exact match is PUBLISHED. If the listing is slow, she waits inside the same call.

Questions, answered

Price

A$0.01 a check, from your GOL balance: the same key and balance as Check. Nothing is charged for a wrong key, bad input, or when npm can't be reached. Top up or get a key.

Install

For Claude Code:

claude mcp add flora --scope user -- npx -y @golproductions/flora mcp

Publish and prove in one step:

npx @golproductions/flora publish

Flora reads your GOL key from the GOL_KEY environment variable, or from ~/.check/key.