pdf-redaction-check

Purpose: Ensuring that sensitive content is permanently removed from PDFs instead of remaining recoverable beneath visual redaction overlays.

Inferred · not functionally tested

Audience: developers and security professionals

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

pdf-redaction-check sits in PulseGate's Malware analysis & digital forensics category. Inferred · not functionally tested: It focuses on ensuring that sensitive content is permanently removed from PDFs instead of remaining recoverable beneath visual redaction overlays. Inferred · not functionally tested: It is built as an open-source project for developers and security professionals. Basis unknown · not verified: pdf-redaction-check is open source under the MIT license. Basis unknown · not verified: pdf-redaction-check is available on the command line, and it can be self-hosted.

Sean The Geek builds and maintains pdf-redaction-check, and it first shipped in 2026. The project is developed in the open on GitHub with 21 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include PDF redaction verification, content removal checks, and redaction forensics.

Summary written by a language model from the project’s public pages.