agentleFS
zxcvbn-tszxcvbn-ts/zxcvbn/CLAUDE.md

zxcvbn

CLAUDE.md1.2k starsChanged 13 days agoMITView on GitHub

Realistic password strength estimation, written in TypeScript — a rewrite of Dropbox's zxcvbn. Yarn workspaces + Lerna monorepo (independent versioning): Faster iteration loops: - yarn -s test:silent [path] — use this when running tests as an AI agent: prints only failures and the summary, hides console output from passing tests, no coverage table - yarn -s test:coverage:silent [path] — the same plus overall coverage percentages, without the per-file table or uncovered lines (yarn test has those) - yarn -s benchmark:silent…

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about zxcvbn-ts/zxcvbn

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub
  • In this repositoryOne other file it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep this file to standing, always-true project facts.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

zxcvbn-ts

Realistic password strength estimation, written in TypeScript — a rewrite of Dropbox's zxcvbn.

Structure

Yarn workspaces + Lerna monorepo (independent versioning):

  • packages/libraries/main — @zxcvbn-ts/core, the estimator itself (matchers, scoring, feedback)
  • packages/libraries/pwned — Have I Been Pwned matcher extension
  • packages/languages/* — one package per language (dictionaries + translated feedback), plus languages/common for shared adjacency graphs, password lists, and diceware data
  • docs/ — VuePress documentation site
  • data-scripts/ — scripts that generate/dedupe language dictionary data

Commands

  • yarn build — build all packages (rollup, via lerna, in parallel)
  • yarn lint / yarn lint:fix — eslint
  • yarn typecheck — tsc --noEmit across the repo
  • yarn test — full vitest suite with coverage (coverage is only collected for packages/libraries/main, even though other packages have their own specs)
  • yarn test:types — attw --pack per package; checks published type resolution
  • yarn docs:dev / yarn docs:build — VuePress docs site
  • yarn release — maintainer-only: tags, pushes and publishes the committed versions. Versions and changelogs are prepared beforehand with the release skill

Faster iteration loops:

  • yarn -s test:silent [path] — use this when running tests as an AI agent: prints only failures and the summary, hides console output from passing tests, no coverage table
  • yarn -s test:coverage:silent [path] — the same plus overall coverage percentages, without the per-file table or uncovered lines (yarn test has those)
  • yarn -s benchmark:silent [--targets local,4.2.0] [--scenarios common,long] — use this when running the benchmark as an AI agent: same measurements and options as yarn benchmark, printed as a compact table
  • yarn -s typecheck / yarn -s lint — -s hides yarn's own noise; there are no agent-specific variants, so output is plain tsc / eslint stylish (absolute paths, grouped per file)
  • npx vitest run packages/libraries/main — just the core package's tests
  • npx tsc --noEmit -p . — typecheck without rebuilding
  • npx lerna exec --scope @zxcvbn-ts/core -- rollup -c ../../../scripts/rollup.config.mjs — build only core

Conventions

  • Node version is pinned in .nvmrc; package manager is Yarn (workspaces).
  • Adding a new language package follows the guide at docs/guide/languages — not duplicated here.
  • A bug that makes a password look stronger than it really is (overestimated guesses) is not lower severity than one that makes it look weaker. Both mislead the user; overestimation is the specific failure mode this library exists to prevent. Fix and test it with the same priority.

Working here

Keep this file to standing, always-true project facts. Anything workflow-specific — a multi-step release process, a one-off migration, a recurring but situational task — belongs in a dedicated skill under .claude/skills/, not appended here: skills load on demand, this file loads on every turn.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.