MiniWho: A Self-Hosted Resume Builder That Actually Keeps Hidden Fields Hidden
Most resume platforms monetize by watermarking, AI processing, or analytics, and hidden fields often amount to front-end CSS. MiniWho eliminates those vectors by design, and for teams or career services that handle sensitive resumes, it offers a self-hosted instance where data never leaves the premises.
MiniWho targets the resume-writing grind: alignment fights in Word, watermarked exports from template sites, and data uploaded to third parties without consent. The project is a self-hosted, open-source resume workbench that stores content as JSON, separates content from layout, and renders A4 pages consistently across screen, print, and PDF. It ships with 18 structured modules and 60 A4 templates, all free, with no paid tiers or third-party analytics.
Privacy is structural, not cosmetic. Phone numbers, emails, and other fields flagged as hidden are stripped from the server response before they reach a visitor's browser. Photos are served via HMAC-signed short-lived URLs, and share links support passwords, expiry, view counts, and revocation. A five-dimension diagnostic scores resumes on completeness, job match, expression quality, quantified results, and format, using fixed local rules with no external AI. The project runs on SQLite by default, switches to MySQL with one environment variable, and self-hosts cleanly with a Docker command that includes Chromium and Chinese fonts for server-side PDF generation.
Template packs are deliberately sandboxed: they contain theme tokens and constrained CSS only, with @import, expression(), behavior, !important, and external url() rejected server-side. That means community templates can't execute code or corrupt someone's resume. The project also documents its honest limits: no Word or Markdown export, no OCR, no AI polishing, and no central template marketplace yet.
MiniWho treats hidden fields as a server-side contract, not a styling choice; that is the difference between a privacy feature and privacy theater.
The template sandbox's approach of physically denying execution capability at the format level makes an open template ecosystem viable without a security review pipeline.
By rewriting only the ToUnicode mapping in the PDF, the project solves the ATS-readable text problem without touching layout, a trade-off many export tools get wrong.
The README's explicit list of unfinished features is more useful than a hyped roadmap, because it sets expectations and points contributors to the gaps.