Redact sensitive fields from HAR files with deterministic reports.
har-redaction-kit is a small TypeScript package for local-first HAR cleanup workflows. It accepts a parsed HAR object or a HAR JSON string, returns a cloned sanitized HAR, and lists every changed path without copying secret values into the report.
- TypeScript types are generated from the source.
- ESM-only package with no runtime dependencies.
- Marked as side-effect free for bundlers.
- Browser-friendly implementation with no Node-only APIs.
- CI runs
npm ci,typecheck,build, andtest. - Tested on Node.js 20 and 22 with GitHub Actions.
npm install har-redaction-kitimport { redactHar } from "har-redaction-kit";
const result = redactHar(harJson, {
placeholder: "[support-redacted]"
});
if (!result.ok) {
console.log(result.diagnostics);
} else {
console.log(result.summary);
console.log(result.changes);
sendToSupport(result.har);
}By default, redactHar redacts:
- request
Authorization,Proxy-Authorization,X-API-Key,X-Auth-TokenandX-CSRF-Tokenheaders; - request
Cookieheaders and responseSet-Cookieheaders; - request and response cookies;
- sensitive query parameters in
request.queryString; - the same sensitive parameters inside
request.url; - sensitive fields in
request.postData.params; - sensitive keys in JSON
request.postData.text; - sensitive keys in
application/x-www-form-urlencodedrequest.postData.text; - sensitive keys in JSON
response.content.text.
The report stores the path, rule, reason, and value lengths. It does not store the original value.
const result = redactHar(JSON.stringify(har));Returns:
type HarRedactionResult =
| {
ok: true;
har: unknown;
changes: HarRedactionChange[];
diagnostics: HarRedactionDiagnostic[];
summary: HarRedactionSummary;
}
| {
ok: false;
har: null;
changes: [];
diagnostics: HarRedactionDiagnostic[];
summary: HarRedactionSummary;
};Expected invalid input returns { ok: false } instead of throwing. Object inputs must be JSON-serializable, which matches the HAR format and avoids mutating circular or non-JSON data.
summary.changedEntries counts HAR entries where at least one request or response value changed. summary.changedRequests is kept as a compatibility alias with the same value.
const redactor = createHarRedactor({
rules: ["authorization-headers", "cookies"]
});
const result = redactor.redact(har);Per-call options override the defaults:
const result = redactor.redact(har, {
placeholder: "[hidden]"
});const byRule = summarizeHarRedactions(result.ok ? result.changes : []);Builds a per-rule count from a saved change list.
import { isHarRedactionRule } from "har-redaction-kit";
if (isHarRedactionRule(configRule)) {
enabledRules.push(configRule);
}Validates user-provided rule names before passing them to redactHar.
import { harRedactionRules } from "har-redaction-kit";
console.log(harRedactionRules);Exports the built-in rule names for UI controls, config validation and documentation.
import { defaultHarSensitiveKeys } from "har-redaction-kit";
console.log(defaultHarSensitiveKeys);Exports the default key names used by query, form and JSON redaction.
| Option | Default | Description |
|---|---|---|
rules |
all built-in rules | Select which redaction rules run. |
placeholder |
[REDACTED] |
Replacement value written into the cloned HAR. |
sensitiveKeys |
common token, secret, session and password names | Query, form and JSON key names to redact. |
sensitiveKeyMatch |
contains |
Use contains for broad matching or exact for stricter integrations. |
maxRedactions |
unlimited | Stop changing values after this count. |
keepOriginalUrl |
false |
Keep request.url unchanged while still redacting queryString. |
Invalid runtime options are ignored with an invalid-options diagnostic instead of throwing. Empty sensitive key names are ignored so they cannot match every key accidentally.
For strict tooling, use exact key matching to avoid broad matches such as key matching monkey:
redactHar(har, {
sensitiveKeys: ["token", "api_key", "session_id"],
sensitiveKeyMatch: "exact"
});type HarRedactionRule =
| "authorization-headers"
| "cookie-headers"
| "cookies"
| "query-sensitive-keys"
| "post-data-sensitive-keys"
| "response-content-sensitive-keys"
| "security-headers";Use rules to run only a subset:
redactHar(har, {
rules: ["authorization-headers", "cookie-headers", "cookies"]
});Diagnostics are stable strings intended for logs, UI hints and tests:
invalid-inputinvalid-jsoninvalid-har-shapeinvalid-optionsunserializable-inputunknown-ruleentry-without-requestentry-without-responseredaction-limit-reached
This package is a deterministic redaction helper, not a complete data-loss prevention system. It does not guarantee exhaustive secret detection.
Use conservative defaults, review the changes report, and add project-specific sensitiveKeys when your system uses custom parameter names.
har-redaction-kit does not:
- read or write files;
- upload HAR data;
- validate the full HAR schema;
- render a HAR waterfall;
- inspect every vendor-specific HAR extension;
- decode and rewrite base64-encoded response bodies;
- mutate circular, BigInt-containing or otherwise non-JSON-serializable object input;
- guarantee that all secrets are removed.
The core is designed for browser workbenches, support tools and thin CLIs.
MPL-2.0