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

@scalang/validate

v0.0.5

Published

Spec verification, English detection, and identifier validation for Scalang with Lingo.dev and Scalar

Readme

@scalang/validate

OpenAPI spec verification for Scalang.

Verifies translated specs for completeness, structural integrity, and translation quality. Detects untranslated content by English-language scoring and validates key identifiers like operationId, tag names, and $ref paths are preserved.

Installation

npm install @scalang/validate

Usage

Verify All Specs

import { verifySpecs } from "@scalang/validate";

const result = await verifySpecs("./public/specs", {
  sourceLocale: "en",
  locales: ["en", "fr", "de"],
  translatableFieldGroups: fieldGroups,
});

if (result.valid) {
  console.log("All specs verified");
} else {
  for (const issue of result.issues) {
    console.warn(
      `[${issue.locale}] ${issue.field}: ${issue.type} — ${issue.message}`
    );
  }
}

Check Individual Aspects

import {
  detectEnglishScore,
  verifyTagNames,
  verifyOperationIds,
  verifyRefs,
} from "@scalang/validate";

// Detect untranslated content (0 = no English, 1 = all English)
const score = detectEnglishScore("Bonjour le monde");
// ~0.0

// Verify tag names match across locales
const tagIssues = verifyTagNames(sourceSpec, translatedSpec, "fr");

// Verify operationIds are preserved
const opIdIssues = verifyOperationIds(sourceSpec, translatedSpec, "fr");

// Verify $ref paths are preserved
const refIssues = verifyRefs(sourceSpec, translatedSpec, "fr");

Verification Pipeline

verifySpecs runs a comprehensive pipeline:

  1. Structure Check — Ensures translated spec has same structure as source
  2. Tag Name Verification — Tag names must not be translated
  3. OperationId Verification — Operation IDs must be preserved
  4. $ref Verification — JSON references must not be translated
  5. English Detection — Flags fields with high English scores in non-English locales
  6. Ref Restoration — Optionally restores broken $ref paths

API

verifySpecs(outputDir, options): Promise<VerificationResult>

Full verification pipeline. Returns { valid: boolean, issues: VerificationIssue[] }.

detectEnglishScore(text: string): number

Returns 0–1 score indicating how likely text is English. Uses common English word frequency analysis.

verifyTagNames(source, translated, locale): VerificationIssue[]

Checks that tag names are unchanged between source and translated specs.

verifyOperationIds(source, translated, locale): VerificationIssue[]

Checks that operationId values are preserved.

verifyRefs(source, translated, locale): VerificationIssue[]

Checks that $ref paths are unchanged.

restoreRefs(source, translated): void

Restores $ref values from source spec into translated spec (mutates in place).

Issue Types

| Type | Description | | ------------------------ | --------------------------------------------- | | untranslated | Field still contains English text | | missing-field | Field exists in source but not in translation | | tag-translated | Tag name was incorrectly translated | | operationId-translated | Operation ID was incorrectly translated | | ref-translated | $ref path was incorrectly translated |

License

MIT