Showing ABS from vPIC Without Inventing Brake-System Safety Grades

NHTSA vPIC often returns anti-lock brake catalog fields on DecodeVinValues-style payloads -- commonly under keys such as ABS when the pattern includes that token. Those strings are useful on a free VIN decode card. The trap is turning a single sourced field into a brake-system safety grade, "ABS verified working," or stopping-distance claim that the catalog never asserted.

This post is about honest display: show the ABS catalog value when vPIC provides it, refuse brake-safety inventing, and allow a clean "not provided" state when the field is empty. Keep ABS catalog tokens separate from brake-pad wear, hydraulic pressure, and road-test stopping distances. A sourced token is still only a token: it does not prove the system is present, calibrated, or undamaged on the listed vehicle. (TPMS and seat-belt honesty are separate topics; here the focus is ABS.)

What ABS is (and is not) in vPIC

ABS (or the equivalent anti-lock brake field your decode maps) is a catalog attribute associated with the VIN pattern. It answers a narrow question: which ABS-related token did the decode associate with this pattern?

It does not answer:

• Whether brakes currently meet a stopping-distance or fade standard
• Whether ABS modules, sensors, or pumps work on this specific vehicle today
• Electronic stability control, traction control, or brake-assist packages you did not source
• Whether a dashboard ABS light is on, off, or silenced after a repair
• A composite "brake safety score" built from missing neighboring fields

Empty ABS does not authorize a default "Standard" badge, and a positive token does not mean "brakes verified safe." Do not fill gaps from Make/Model/Year folklore or a chart keyed only by model year.

Normalize empties, do not invent grades

Treat blank, "Not Applicable", "N/A", and similar tokens as missing. Keep a sourced string when present; do not rewrite it into "ABS Grade A" or a brake-inspection score.

const EMPTY = new Set([
  "",
  "not applicable",
  "n/a",
  "na",
  "null",
  "none",
  "unknown",
]);

export type AbsView = {
  value: string | null;
  source: "vpic" | "missing";
};

export function viewAbs(fields: {
  ABS?: string | null;
}): AbsView {
  const raw = (fields.ABS ?? "").trim();
  if (!raw || EMPTY.has(raw.toLowerCase())) {
    return { value: null, source: "missing" };
  }
  return { value: raw, source: "vpic" };
}

export function absLines(view: AbsView): string[] {
  if (view.source === "missing") {
    return ["ABS: not provided by vPIC for this VIN"];
  }
  return [
    `ABS (vPIC): ${view.value}`,
    "Catalog token only -- not a brake-system safety grade",
  ];
}

The footnote matters. Buyers over-read a single ABS field as verified stopping performance. Show the sourced token; if blank, say "not provided" -- no greyed "Standard" and no invented brake grade.

Forbidden upgrades

Product pressure often asks for:

1. Mapping any non-empty ABS into "anti-lock brakes verified"
2. Inventing IIHS / Euro NCAP / star-equivalent brake-safety language from the catalog field
3. Bundling ABS with ESC or traction-control keys into "Full Brake Safety Package"
4. Defaulting blank ABS to "Standard" so mid-trim cars look complete
5. Renaming catalog tokens into OEM brake-suite marketing names you did not source

Refuse those. If you show neighboring catalog fields from separate sourced keys, show each on its own row. Never invent stopping-distance or package language inside the ABS mapper.

export function assertNoAbsBrakeInvent(moduleSource: string): void {
  const banned = [
    /abs verified/i,
    /brake.?system safety grade/i,
    /stopping distance/i,
    /iihs/i,
    /full brake safety/i,
    /euro ncap/i,
  ];
  for (const re of banned) {
    if (re.test(moduleSource)) {
      throw new Error(
        `ABS module must not invent brake grades: ${re}`,
      );
    }
  }
}

export type CardRow = { label: string; value: string };

export function cardRows(fields: {
  ABS?: string | null;
  ESC?: string | null;
  TractionControl?: string | null;
}): CardRow[] {
  const view = viewAbs(fields);
  const out: CardRow[] = [];
  if (view.source === "missing") {
    out.push({ label: "ABS", value: "not provided" });
  } else {
    out.push({ label: "ABS", value: String(view.value) });
  }

  const esc = (fields.ESC ?? "").trim();
  if (esc && !EMPTY.has(esc.toLowerCase())) {
    out.push({ label: "ESC (vPIC)", value: esc });
  }
  const tc = (fields.TractionControl ?? "").trim();
  if (tc && !EMPTY.has(tc.toLowerCase())) {
    out.push({ label: "Traction control (vPIC)", value: tc });
  }
  return out;
}

Keep neighboring catalog fields on their own labeled rows. Never concatenate them into "Full Brake Safety Package," and never treat a separate ESC catalog key as proof that ABS implies a safety grade.

UI copy that stays honest

Prefer:

• "ABS (vPIC): Standard"
• "ABS: not provided by vPIC for this VIN"
• A short footnote: catalog token, not a brake-system safety grade

Avoid:

• "IIHS brake safety Superior -- verified"
• "ABS Grade A included"
• Grey placeholders that look like real ABS data when the field was empty

Quick checks

import assert from "node:assert/strict";

assert.equal(viewAbs({}).source, "missing");
assert.deepEqual(absLines(viewAbs({})), [
  "ABS: not provided by vPIC for this VIN",
]);

const std = viewAbs({ ABS: "Standard" });
assert.equal(std.value, "Standard");
assert.ok(
  absLines(std).some((l) => /not a brake-system safety grade/i.test(l)),
);
assert.ok(
  !absLines(std).some((l) =>
    /iihs|abs verified|brake safety package/i.test(l),
  ),
);

const rows = cardRows({
  ABS: "",
  ESC: "Standard",
  TractionControl: "Standard",
});
assert.ok(
  rows.some((r) => r.label === "ABS" && r.value === "not provided"),
);
assert.ok(rows.some((r) => r.label.includes("ESC")));
assert.ok(rows.some((r) => r.label.includes("Traction")));
assert.ok(!rows.some((r) => /iihs|abs verified/i.test(r.value)));

Review rule: ABS modules must not contain brake-upgrade or safety-grade phrases except in forbidding tests. Never upgrade a blank into "Standard."

Takeaway

ABS is a catalog token. Display it with clear sourcing, allow "not provided," and never use it as a key into invented brake-system safety grades, stopping-distance claims, or "full brake safety" bundles. Your free VIN UI stays trustworthy when ABS data is either a real vPIC value with a modest footnote -- or absent -- and brake-performance marketing lives somewhere else, clearly labeled, or not at all.

I maintain VIN Lookup, a free VIN decode based on NHTSA data.