Classify incident records from a policy and an incident export, both supplied as local JSON files. The tool makes the four dimensions and the rule behind each severity visible. It is useful when teams need a reproducible classification review; it does not decide whether an incident is safe or resolved.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+.
Run the checked-in example
node bin/incident-severity-normalizer.mjs --policy examples/clean/policy.json --incidents examples/clean/incidents.json --jsonRead the result
That complete example exits 0. The first row's original severity is SEV2, with a separately retained reviewed override to SEV3; the second is a complete SEV1. pass means classification completed, not that either incident is safe.
Scope
This is a policy-based classification of an exported snapshot, not a live incident-management integration or a recommendation to downgrade an incident. It cannot infer a missing impact, verify whether the export is current, judge the policy's appropriateness, or validate a free-form explanation for an override. It does not contact a host or database, execute actions, or write a report file. Treat incomplete as a request for better evidence, not as absence of severity.