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

dev-lang-db

v0.1.0

Published

Detect unnatural / broken translations in your locale files — placeholders, untranslated strings, wrong script, repeats and more — with ZERO LLM. Optional AI layer only when you want fix suggestions. Works in any JS/TS project (frontend or Node backend).

Readme

lang-natural

Detect unnatural / broken translations in your locale files — with zero LLM. Catches dropped placeholders, untranslated strings, wrong script, repeated words, markup drift and length anomalies. Runs fully offline, no API key. An optional AI layer (--fix) suggests natural rewrites only when you ask.

Works in any JavaScript/TypeScript project — a Next.js/React frontend or a Node backend.

Install

npm install -D lang-natural

Configure — lang-natural.config.js

export default {
  localesDir: "./messages",
  sourceLocale: "en",
  targetLocales: ["ar", "es", "hi"],
  failOn: "error",   // error | warning | info
};

Run

npx lang-natural            # scan and print the report
npx lang-natural --json     # machine-readable output
npx lang-natural --fix      # LLM fix suggestions (needs GEMINI_API_KEY)

Exit code is 1 when blocking issues are found — so it fails CI.

Use in code

import { detect } from "lang-natural";

const issues = detect({
  key: "cart.itemCount",
  locale: "ar",
  source: "You have {count} items",
  candidate: "لديك عناصر",
});
issues.forEach((i) => console.log(i.severity, i.message));

What the local (no-LLM) detector catches

  • Empty translations
  • Missing / extra placeholders ({count}, {{name}}, %s)
  • Strings identical to the source (untranslated)
  • Wrong script (Latin text in an Arabic/Hindi/… locale)
  • Repeated words
  • HTML/markup that differs from the source
  • Length outliers vs. the locale's typical ratio

Subtle word-order naturalness and rewrite suggestions require the optional LLM layer (--fix).

CI (GitHub Actions)

- run: npx lang-natural           # no key needed for detection

MIT