Security Changelog
A plain-language record of the security work we’ve shipped.
These entries are intentionally high-level. We do not publish the specific details of individual findings or fixes — file names, exact techniques, or version numbers — because that would hand an attacker a roadmap to our customers’ data. We describe the kind of improvement, and we move quickly behind the scenes.
June 2026
Continuous scanning + evidence trail
- Added automated secret, static-analysis, and dependency scanning to every code change, plus a pre-commit gate that stops secrets before they enter the codebase.
- Stood up a weekly hands-off security scan that records results to an append-only evidence log, supporting our SOC 2 readiness work.
- Hardened API input validation across data-access paths and tightened our Content Security Policy.
- Upgraded dependencies to clear known advisories.
Earlier 2026
Foundational hardening
- Enforced TLS everywhere with long-lived HSTS, and added a full set of application security headers.
- Locked down the database with Row-Level Security and removed anonymous access.
- Added optional two-factor authentication and a role-and-permission system.
- Published a Trust Center and a responsible-disclosure policy.
See our Trust Center for our current security posture, or report a vulnerability. PlateMastr LLC — Last updated June 2026.