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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@coinsmart/wallet-validator

v1.0.0

Published

## The problem

Downloads

6

Readme

Wallet-validator

The problem

There are hundreds of npm libraries that try to validate wallet addresses only by the coin/token name making it impossible to cover them all. A fork adds 3 new tokens and the problem is still there.

This solution

Rather than validating coins or tokens by name, we try to do it by chain name whenever it is possible. This way we can cover all tokens on a specific chain and the library is easier to maintain.

It is also better to specify a chain name for validation rather than a coin name, this way you can be sure that the network you are using matches the input address.

You can check https://coinmarketcap.com/ to know the chain of a token.

Usage

import { validate } from 'wallet-validator'

validate('0xa00354276d2fC74ee91e37D085d35748613f4748', 'ETH') // true
validate('14GwrqiECaY7iizoHdscCVF2j14tYn7eKE9Fbvn7PHdTABkf', 'Polkadot') // true
validate('5GrpknVvGGrGH3EFuURXeMrWHvbpj3VfER1oX5jFtuGbfzCE', 'Polkadot') // true
validate('CpjsLDC1JFyrhm3ftC9Gs4QoyrkHKhZKtK7YqGTRFtTafgp', 'Polkadot') // true
validate('12QeMLzSrB8XH8FvEzPMVoRxVAzTr5XM2y', 'btc') // true

Troubleshooting

  • Unable to validate Polkadot/Kusama addresses on React native: See https://polkadot.js.org/docs/usage/FAQ#under-my-babel-build-i-have-a-bigint-to-number-conversion-error for more information. If you are on React Native, one solution is to patch package babel config. See: https://github.com/polkadot-js/common/issues/1321#issuecomment-1000194727
  • TypeError: (0 , util_1.isHex) is not a function: If you're using CRA, You need to install react-app-rewired and add this to your config-overrides.js file:
    config.module.rules.push({
      test: /\.cjs$/,
      include: /node_modules/,
      type: 'javascript/auto'
    })

Tests

npm t to run the tests.