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

package-author-parse-kit

v0.1.0

Published

Parse package author strings with structured diagnostics.

Readme

package-author-parse-kit

License: MPL-2.0 CI

Parse package author, maintainer, and contributor strings into structured fields with diagnostics.

Demo

Try the browser preview: packages.wasta-wocket.fr/package-author-parse-kit.

Package quality

  • TypeScript types are generated from the source.
  • ESM-only package with no runtime dependencies.
  • Marked as side-effect free for bundlers.
  • CI runs npm ci, typecheck, build, and test.
  • Tested on Node.js 20 and 22 with GitHub Actions.
  • Browser-friendly implementation with no Node-only APIs.

Install

npm install package-author-parse-kit

Usage

import { parsePackageAuthor } from "package-author-parse-kit";

const result = parsePackageAuthor("Ada Lovelace <[email protected]> (https://example.dev)");

if (result.ok) {
  result.author.name;
  result.author.email;
  result.author.url;
}

Invalid input returns stable issue codes instead of throwing:

const result = parsePackageAuthor("Ada <not-an-email>");

result.ok; // false
result.issues[0]?.code; // "invalid-email"

Non-string runtime values are rejected with invalid-input instead of being coerced into names. Runtime-invalid options return an invalid-options diagnostic rather than throwing.

API

parsePackageAuthor(input, options?)

Returns a discriminated result with:

  • author: parsed name, email, and url fields.
  • tokens: field tokens with source offsets.
  • issues: stable diagnostics when parsing fails.

packageAuthorOrUndefined(input, options?)

Returns the parsed author object, or undefined when validation fails.

isPackageAuthor(input, options?)

Returns true when the string can be parsed without diagnostics.

stringifyPackageAuthor(author)

Formats an object as Name <email> (url).

Options

  • maxInputLength: reject long input before scanning. Default: 500.
  • requireKnownField: reject input that does not produce any known field. Default: false.
  • allowBareUrl: parse a bare https://, http://, or mailto: value as a URL. When disabled, a bare URL returns a bare-url-disabled diagnostic instead of being treated as a name. Default: true.

Supported Inputs

Browser Compatibility

The core parser uses only strings, arrays, regular expressions, and plain objects. It has no runtime dependencies and does not use Node APIs.

CLI

No CLI is included in this draft. The natural use case is package metadata validation inside applications, build tools, and browser-based package editors.