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

@openbasedata/currencies

v1.0.0

Published

Open base data for world currencies

Readme

Currencies Open Base Data

npm version npm downloads

How To Use

npm install @openbasedata/currencies

data.json contains currency metadata with code, name, and symbol, etc.

Other localized translations are split into /translations/<locale>.json (one language per file) to keep the main dataset smaller.

Data Structure

[
  {
    "code": "CNY",
    "codeNumeric": "156",
    "name": "Chinese Renminbi Yuan",
    "nativeName": "人民币",
    "symbol": "¥"
  }
]

| Field | Type | Required | Description | | ------------- | -------- | -------- | --------------------------------------------------------------------------- | | code | string | Yes | ISO 4217 alphabetic currency code (3 uppercase letters), e.g. CNY. | | codeNumeric | string | Yes | ISO 4217 numeric currency code (3-digit string, zero-padded), e.g. "156". | | name | string | Yes | English currency name. | | nativeName | string | Yes | Currency name in the native language of the issuing country. | | symbol | string | Yes | Commonly used currency symbol, e.g. ¥. |

Translations

Translations are stored in /translations, one file per locale (for example: /translations/zh-Hans.json, /translations/fr.json). English is stored directly in data.json.

Each translation file has this structure:

{
  "CNY": {
    "name": "Chinese Renminbi Yuan"
  }
}