Resources

What this site is built on, and where its data comes from.

Packages

ncic-vehicle-lookup

Synchronous NCIC vehicle code lookups — make, model, colour and style — from NIEM 6.0, resolving in both directions, with zero runtime dependencies. It powers every NCIC feature on this site.

npm GitHub

vin-test-data

547,706 real, validated VINs with make, model, year, body type and fuel type, plus a CLI. For tests and decoder benchmarks where real VINs are needed. It is used here for build-time validation, not as a VIN source — nothing this site serves comes from it.

npm GitHub

@cardog/corgi

Offline VIN decoding powered by VPIC, under the ISC licence. It is what turns a VIN into a make, model and plant here, with no network call and no third-party API.

npm GitHub

Using ncic-vehicle-lookup

The NCIC tables on this site come from this package. It is a plain dependency with no runtime requirements, so it works the same in a script, a server, or a test.

npm install ncic-vehicle-lookup

import { vehicleMake, vehicleColor } from 'ncic-vehicle-lookup';

vehicleMake.getCode('Toyota');   // 'TOYT'
vehicleMake.getName('TOYT');     // 'Toyota'
vehicleColor.getCode('Black');   // 'BLK'

Data sources

NHTSA VPIC — the vehicle product information catalogue behind every decode and every generated pattern. It covers US-market vehicles only.
NIEM 6.0 — the National Information Exchange Model, the source of the NCIC make, colour and style code tables.

Standards

ISO 3779 — the 17-character VIN, and the WMI, VDS and VIS sections it divides into.
ISO 4030 — where and how a VIN is located and marked on a vehicle.
49 CFR Part 565 — the United States federal VIN requirements, including the check digit that ISO 3779 leaves optional.