</>PackageGraphPackageGraph

punycode

npmv2.3.1

A robust Punycode converter that fully complies to RFC 3492 and RFC 5891, and works on nearly all JavaScript platforms.

Adopt with care

punycode is usable, with caveats. Last published 1045 days ago.

  • AAdoption: grade A, Excellent.

    148.9M downloads per week and 2 known dependents.

  • DMaintenance: grade D, Poor — a real concern.

    Last published 1045 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 33 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding punycode to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

33 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >=6
Module format
ESM + CommonJS
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the punycode README.

jsFull README ↗
const punycode = require('punycode/');

punycode vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
punycodethis page148.9M2MIT2 years ago
tr46192.6M1MIT1 day ago
@jridgewell/resolve-uri166.3M1MIT1 day ago
encodeurl133.6M5MIT1 day ago
open130.4M4MIT1 day ago
follow-redirects91.6M2MIT1 day ago

Dependencies

Declared by punycode v2.3.1. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (3)

codecov ^3.8.3mocha ^10.2.0nyc ^15.1.0

Used by

Popular packages that depend on punycode.

tr46npm

An implementation of the Unicode UTS #46: Unicode IDNA Compatibility Processing

↓ 192.6M/wk◈ 1 dependents⚖ MIT
@exodus/bytesnpm

Various operations on Uint8Array data

↓ 0/wk◈ 5 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of punycode.

tr46@exodus/bytespunycode
punycode dependencies dependents

Frequently installed together

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
@noble/hashesnpm

Audited & minimal 0-dependency JS implementation of SHA, RIPEMD, BLAKE, HMAC, HKDF, PBKDF & Scrypt

↓ 59.6M/wk◈ 1 dependents⚖ MITTS
esbuildnpm

An extremely fast JavaScript and CSS bundler and minifier.

↓ 242.4M/wk◈ 42 dependents⚖ MITTS
base64-jsnpm

Base64 encoding/decoding in pure JS

↓ 0/wk◈ 3 dependents⚖ MITTS
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
iconv-litenpm

Convert character encodings in pure javascript.

↓ 0/wk◈ 6 dependents⚖ MITTS
@petamoriken/float16npm

IEEE 754 half-precision floating-point for JavaScript

↓ 0/wk◈ 2 dependents⚖ MITTS

Release history

No releases in the last two years, typically about 100 days apart.

Recent versions of punycode
VersionPublishedSizeLicense
2.3.1latest2 years ago33 KBMIT
2.3.03 years ago32 KBMIT
2.2.23 years ago32 KBMIT
2.2.03 years ago32 KBMIT
2.1.18 years ago32 KBMIT
2.1.09 years ago—MIT
2.0.110 years ago—MIT
2.0.010 years ago—MIT
1.4.110 years ago—MIT
1.4.010 years ago—MIT
1.3.212 years ago—MIT
1.3.112 years ago—MIT
1.3.012 years ago—MIT
1.2.412 years ago—MIT
1.2.313 years ago—MIT

Overview

punycode is an npm package that a robust Punycode converter that fully complies to RFC 3492 and RFC 5891, and works on nearly all JavaScript platforms. It is extremely widely used, with about 148.9M downloads per week and 2 known dependents in the graph. The latest version is 2.3.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need a robust Punycode converter that fully complies to RFC 3492 and RFC 5891, and works on nearly all JavaScript platforms and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (148.9M weekly downloads).
  • Clear open-source license (MIT).
  • Lean dependency tree (3 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

google-wombotmathias

Keywords

dnsdomainidnidnapunycodeunicodeurl

Frequently asked questions

Should I use punycode?

punycode is usable, with caveats. Last published 1045 days ago.

How do I install punycode?

Run `npm install punycode` to add punycode to your npm project.

What license is punycode released under?

punycode is distributed under the MIT license.

How popular is punycode?

punycode has approximately 148,934,141 downloads per week and 2 known dependent packages.

Is punycode still maintained?

The most recent release of punycode (v2.3.1) was published 2 years ago.

Does punycode run install scripts?

No. punycode does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.