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

@tatastu/mark

v0.1.6

Published

One API call stamps any content with a permanent, publicly verifiable provenance record.

Readme

Mark

npm version service status license

Signed provenance for exact files, independent of the Tatastu app. Hash locally, get a signed receipt, and keep a downloadable verification bundle after daily anchoring. Mark records a signer's claim about exact bytes; it does not prove original authorship, detect AI generation, or certify legal compliance. See the transparency guide for how provenance can support an AI disclosure workflow and where it falls short.

import { stamp, hashText } from "@tatastu/mark"

const hash = await hashText("Hello, world!")
const receipt = await stamp({ contentHash: hash, title: "My post", apiKey: process.env.MARK_API_KEY })
console.log(receipt.verifyUrl)
// → https://makemark.io/p/proof_1m5h...

Live service: makemark.io — verification is always free. Open the printed verifyUrl in a browser to see the public record: signer, timestamp, and the public anchor once it lands (Arweave by default; Base only when present). This package is the MIT-licensed client and offline verifier for that service.

For people: sign in at makemark.io/account, choose a file, and use the included monthly allowance without creating an API key. The file is hashed in the browser and never uploaded. API keys are portable credentials for agents, scripts, and other applications.


What it does

A stamp takes the SHA-256 of any content (text, file, JSON, code, binary) and records:

  • Who signed it (a creator identity you provide, or anonymous)
  • When it was signed (millisecond-precision, bounded by the daily Merkle anchor)
  • An Ed25519 signature from the Mark service's key-transparency log

Stamps are queued for daily RFC 6962 Merkle batching and anchoring to Arweave. Base is an optional additional witness, not currently enabled. Download the bundle after anchoring to check the receipt signature and Merkle path offline. Checking a public anchor's existence or publication time requires independent ledger access.

What a stamp does not prove: authorship truth. The service records "this signer claimed this content at this time." The claimed time (signedAt) and proven time (anchored) are distinct and both shown on every verify page.


Install

npm install @tatastu/mark

Quickstart

Stamp text

import { stamp, hashText } from "@tatastu/mark"

const hash = await hashText("The report content goes here.")
const receipt = await stamp({ contentHash: hash, title: "Q3 Report", apiKey: process.env.MARK_API_KEY })
console.log(receipt.verifyUrl)   // https://makemark.io/p/proof_...
console.log(receipt.byline)      // "Verified · https://makemark.io/p/proof_..."

Stamp a file (Node.js)

import { stamp, hashNodeBuffer } from "@tatastu/mark"
import { readFile } from "node:fs/promises"

const bytes = await readFile("./report.pdf")
const receipt = await stamp({
  contentHash: await hashNodeBuffer(bytes),
  contentType: "application/pdf",
  title: "Q3 Financial Report",
  apiKey: process.env.MARK_API_KEY,
})

Verify any content

import { verify, hashText } from "@tatastu/mark"

const { proofs } = await verify(await hashText("The report content goes here."))
if (proofs.length > 0) {
  console.log("Authentic:", proofs[0].verifyUrl)
  console.log("Status:", proofs[0].status)   // SIGNED | ANCHORED | CONFIRMED
}

Stamp a file from a browser app (drag-and-drop)

Stamping needs an API key, and a key in browser code is a leaked key. Hash the file in the browser, send only the hash to your own server, and call stamp() there:

// Browser: the file never leaves the device
import { hashBlob } from "@tatastu/mark"

const file = dropEvent.dataTransfer.files[0]
await fetch("/api/stamp", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({ contentHash: await hashBlob(file), title: file.name }),
})
// Server: holds the key
import { stamp } from "@tatastu/mark"

const receipt = await stamp({ contentHash, title, apiKey: process.env.MARK_API_KEY })

Stamping by hand? Sign in at makemark.io/account instead.


MCP (agent use)

Add makemark.io/mcp to your Claude Code, Cursor, or Windsurf config:

{
  "mcpServers": {
    "mark": {
      "url": "https://makemark.io/mcp"
    }
  }
}

The agent can then call create_account, create_proof, verify_proof, list_proofs, revoke_proof, get_balance, and buy_stamps directly. See the MCP section of the docs for the full config and tool reference.


Keys, errors, and buying stamps

A self-serve key (POST https://makemark.io/keys) comes with one free stamp per network: its freeStamp field says whether this key still has it. Signed-in accounts at makemark.io/account get 3 free stamps a month.

Every failed call throws a ProofError with code (the service's error), status, and the full JSON body, so you can follow its hints:

import { stamp, buyStamps, getBalance, ProofError } from "@tatastu/mark"

try {
  await stamp({ contentHash, apiKey })
} catch (err) {
  if (err instanceof ProofError && err.code === "invalid_api_key") {
    // mistyped or revoked: create a new key (POST https://makemark.io/keys)
  } else if (err instanceof ProofError && err.status === 402) {
    // out of stamps: a person pays the link, then the stamps land on this key
    const { url } = await buyStamps("bundle_5", apiKey)
    console.log(`Pay here: ${url}`)
    // poll until they arrive
    console.log((await getBalance(apiKey)).balance)
  }
}

A 402 body also carries accepts, the x402 payment requirements, if your code would rather pay per stamp in USDC on Base and retry with a PAYMENT-SIGNATURE header.


EU AI Act compliance

EU AI Act Article 50(2) concerns machine-readable marking and detection of synthetic outputs. Mark can support a provenance workflow, but a stamp alone does not establish compliance or detect AI generation.

import { stamp, hashText } from "@tatastu/mark"

const aiOutput = "AI-generated text goes here."
const receipt = await stamp({
  contentHash: await hashText(aiOutput),
  apiKey: process.env.MARK_API_KEY,
})

const labeledOutput = {
  text: aiOutput,
  _proof: {
    contentHash: receipt.contentHash,
    proofId: receipt.proofId,
    verifyUrl: receipt.verifyUrl,
    signedAt: receipt.signedAt,
    bylineHtml: receipt.bylineHtml,
  },
}

Create a key at Mark accounts or with POST /keys, then provide it as MARK_API_KEY. The fingerprint covers the original text, not the JSON wrapper or a transformed copy.

See the transparency guide for limitations.


How verification works

Every stamp is:

  1. Signed immediately with an Ed25519 key from the service's transparency log
  2. Batched daily into an RFC 6962 Merkle tree (0x00/0x01 domain-separated prefixes)
  3. Anchoring: the batch's Merkle root is queued for public anchoring
  4. Confirmed when the configured witness requirements are met (Arweave by default)

Base calldata is an optional additional witness. Record pages name only witnesses that actually have transaction references for that record.

Offline checks and independent witnesses

  1. Ed25519 signature: checks the receipt against the bundled service public key
  2. RFC 6962 Merkle inclusion: checks inclusion in the bundled Merkle root
  3. Public anchor: independently compare that root with the Arweave manifest (and Base calldata only when present) to establish a witnessed time bound

The offline verifier performs the first two checks, plus creator binding when present. It does not fetch ledger state, confirm that or when an anchor was published, or independently validate the key-transparency log. Keep the original file and bundle; separately check public anchors and key provenance when your trust requirements call for them.


Offline verification

After daily anchoring, download the bundle once. The verifyOffline call below makes no network calls; getBundle still needs the service:

import { getBundle, hashNodeBuffer } from "@tatastu/mark"
import { verifyOffline } from "@tatastu/mark/verify/offline"
import { readFile } from "node:fs/promises"

const bytes = await readFile("./report.pdf")
const bundle = await getBundle("proof_1m5h...")
const result = await verifyOffline(bundle, await hashNodeBuffer(bytes))
console.log(result.valid, result.signatureVerified, result.merkleVerified)

The verifier (@tatastu/mark/verify/offline) is a single self-contained module with zero dependencies. It uses only the Web Crypto API (SubtleCrypto), available in Node 18+, Deno, and modern browsers.


Pricing

| Tier | Price | Stamps | Status | |------|-------|--------|--------| | First stamp | $0 | 1 lifetime sample per durable account | Live | | Signed-in Mark account | $0 | 3/month included | Live | | Prepaid packs | $1 / $1.50 / $5 / $8 | 5 / 10 / 50 / 100 (no expiry) | Live | | Volume packs | $35 / $65 / $120 | 500 / 1,000 / 2,000 (no expiry) | Live | | Pay-per-stamp (x402) | $0.10, or $0.05 with API key | one stamp | Live |

Verification is always free and requires no account.

The checkout page reveals only packs that the live offer manifest reports as available. Full, always-current pricing: makemark.io/pricing.


Integrations

| Target | Where | |---|---| | REST API: every endpoint, error table, rate limits | makemark.io/docs | | MCP (Claude Code, Cursor, Windsurf) | makemark.io/docs#mcp, server at https://makemark.io/mcp | | ChatGPT Actions (OpenAPI 3.1) | makemark.io/.well-known/gpt-actions.json | | EU AI Act transparency guide | makemark.io/eu-ai-act |


Support and security

Questions and bug reports: [email protected]. Report a suspected vulnerability privately to the same address with a subject starting [security]. Anything that could let a proof be forged, a signature be misverified, or an offline-verification bundle be accepted when it shouldn't be deserves a private report first.

License

MIT. The license text ships in the package as LICENSE; you can read it on the Code tab.