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 🙏

© 2024 – Pkg Stats / Ryan Hefner

numbering-plans

v2.7.0

Published

International Numbering Plans

Downloads

3

Readme

Numbering plans

Build Status

Goals

This project aims to build a list of international numbering plans for the purposes of:

  • building dialing plans for customers, preventing to flag missing routes where the customer actually misdialed;
  • helping to build LCR routing tables;
  • helping to build rating tables.

It aims to be updated regularly to adapt to changes in international numbering plans. Contributions are welcome in the form of a Pull Request on github!

Validating numbers

var numbers = require('numbering-plans')

numbers.validate('12123141212')
# returns:
# { min: 10, max: 10, mixed: true, geographic: true, name: 'NY',
#   country: 'us', conterminous: true, national_name: 'NANPA',
#   full_name: 'NY (NANPA)' }

numbers.validate('33612341234')
# { max: 9, min: 9, mobile: true, country: 'fr',
#   national_name: 'France', full_name: 'France' }

numbers.validate('33_112')
# { max: 3, min: 3, special: true, emergency: true,
#   country: 'fr', national_name: 'France', full_name: 'France' }

numbers.validate('3397234713')
# false → number is invalid

numbers.validate('4372617278')
# null → unable to decide

Conventions

Available fields, where applicable, are:

  • min: minimum length of national number
  • max: maximum lenght of national number

One of:

  • block -- non-dialable, non-routable, etc.
  • fixed
  • mobile
  • 'mixed' -- could be fixed or mobile (e.g. NANPA)
  • special
  • value_added

For mixed:

  • geographic might be true (e.g. US geographic numbers) or false (e.g. US non-geo)
  • corporate might be true

For fixed:

  • geographic
  • corporate

For value_added:

  • freephone
  • shared_cost
  • personal
  • premium
  • adult

For special:

  • voicemail
  • test
  • vpn
  • emergency

If a field is absent its value is assumed to be false.

Other fields might be available for specific destinations.

The numbering plans are established with the convention that national-only, short numbers, etc. are routed using _ as a separator between the country-code and the national number.