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

@jsonlint/core

v0.1.1

Published

Diagnostics-grade JSON engine: every error in one pass, with locations, hints, and recovery. Zero dependencies, no install scripts.

Downloads

75

Readme

@jsonlint/core

CI

The JSON engine behind jsonlint.com. Every error in one pass — with locations, hints, and recovery — at 25-40x the speed of the legacy jsonlint package. Zero dependencies. No install scripts.

import { validate, tryParse, parse } from "@jsonlint/core";

const { ok, diagnostics } = validate(text, { mode: "jsonc" });
// diagnostics: [{ code: "W060", message: 'duplicate object key "name"',
//                 severity: "warning", start: 41, end: 47,
//                 related: { start: 12, end: 18 },
//                 hint: "the last occurrence wins; ..." }]

Why

  • Every error, one pass. Recovery-based parsing reports all problems, not just the first.
  • Errors that teach. 'True' is not valid JSON — this looks like a Python literal. Smart quotes, trailing commas, unquoted keys, concatenated documents: named, located, and hinted.
  • Catches what parsers can't say. Duplicate keys (with the first occurrence's location), integer precision loss (1111111111258928239 becomes 1111111111258928300), UTF-16-encoded files, BOMs.
  • Safe by default. __proto__ never pollutes; depth limits; duplicate-key policy.
  • JSON.parse compatible. parse() matches native output (reviver included) and throws SyntaxError.
  • Fast. Pure-JS today (validates faster than JSON.parse allocates); Rust/WASM core lands behind the same API.

API

validate(input, opts){ ok, diagnostics } — fastest; powers jsonlint.com tryParse(input, opts){ ok, value, diagnostics } — never throws; value recovered even on errors parse(input, opts) → value or throws — drop-in for JSON.parse lineColumn(src, offset){ line, column }

Input: string, Uint8Array, or ArrayBuffer (UTF-16/32 bytes detected and reported cleanly). Options: mode: "strict" | "jsonc", duplicateKeys: "warn" | "error" | "allow", protoKeys, maxDepth, reviver.

Conformance

JSONTestSuite 95/95 valid accepted, 188/188 invalid rejected; the complete historical test corpora of zaach/jsonlint and @prantlf/jsonlint; regression tests named for the GitHub issues they resolve (see the engine repo's ISSUE_AUDIT.md).

About

By Todd Garland, who has run jsonlint.com for many years. Engineered in collaboration with Claude Fable 5 (Anthropic). Every claim here is backed by tests running in public CI: github.com/toddynho/jsonlint-core — including the full audit of 411 issues across six predecessor projects (ISSUE_AUDIT.md) and the hardening report (HARDENING.md).

MIT