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

ibanforge

v2.1.0

Published

IBAN validation with EMI/virtual-IBAN detection. Zero dependencies, offline, 89 countries: mod-97 (ISO 13616), BBAN parsing, SEPA + VoP reachability, and issuer classification (Wise, Revolut, N26, Monzo...).

Readme

ibanforge

IBAN validation with EMI / virtual-IBAN detection. Zero dependencies, fully offline.

npm install ibanforge
import { validate, classifyIssuer } from 'ibanforge';

validate('CH10 0023 0000 0000 1234 5');
// { iban: 'CH1000230000000012345', valid: true,
//   country: { code: 'CH', name: 'Switzerland' },
//   check_digits: '10',
//   bban: { bank_code: '00230', account_number: '000000012345' },
//   sepa: { member: true, schemes: ['SCT','SDD'], vop_required: false },
//   formatted: 'CH10 0023 0000 0000 1234 5',
//   enrich: { hint: 'Bank name, BIC/SWIFT, Swiss SIX clearing rails and sanctions
//                    screening cannot be computed offline — resolve them at …',
//             free_tier: '200 requests/month, no card',
//             docs: 'https://ibanforge.com/docs' } }

classifyIssuer('TRWIGB2L');   // { type: 'emi', name: 'Wise' }

What it does

  • mod-97 validation (ISO 13616) and BBAN parsing for 89 countries
  • SEPA membership and VoP obligation (EU 2024/886) per country
  • EMI / virtual-IBAN detection — tells a real bank apart from Wise, Revolut, N26, Monzo or Modulr
  • BIC format validation (ISO 9362)
  • A coarse, editorial country risk indicator for AML/CFT triage, offline

What it does not do

The checksum proves an IBAN is well-formed. It cannot tell you who the bank is. That needs a database, and this library ships none:

| Question | Here | Needs data | |---|---|---| | Is this IBAN well-formed? | yes | | | Is this BIC an EMI / digital bank? | yes | | | Is this IBAN a virtual IBAN from an EMI? | | api.ibanforge.com — needs IBAN → BIC | | Which bank is behind it? | | api.ibanforge.com | | Swiss SIX clearing rails, QR-IID? | | api.ibanforge.com | | Is the bank sanctioned (OFAC/EU/UN)? | | api.ibanforge.com |

Every valid result carries an enrich field pointing there. The free tier is 200 requests/month, no card.

getCountryRisk deserves the same candour. It is a hand-maintained editorial judgement, not a reproduction of the FATF or EU lists — it does not track them entry for entry, and it is only as fresh as its last edit. Treat it as a coarse triage signal to layer on top of a live screening feed, never as a substitute for one.

Licence

MIT