Security / 2026 / Runs natively
TimeCapsule Vault
A CLI vault that encrypts a payload until a chosen date, binding the unlock date into the authenticated data so it cannot be edited after the fact.
01
The problem
A sealed file is only as trustworthy as the field holding its unlock date. If that date is plain metadata, anyone can move it.
02
How I approached it
scrypt derives the key from the passphrase and a per-capsule salt, then AES-GCM encrypts with the version, algorithm, unlock date and creation date all passed as additional authenticated data. Changing the date afterwards makes the tag fail and the capsule refuses to open at all.
03
The outcome
Edit the unlock date after sealing and the GCM tag no longer verifies, so the capsule refuses to open at all rather than opening early. Tampering turns into a hard failure instead of a silent success.
Related work
A defensive web-security assessment platform: passive scans of headers, cookies, TLS, DNS and technology hints, graded A–F with a remediation report.
A resume analyser that reads a CV the way an applicant tracking system does, scores each bullet on Google's X-Y-Z formula, and measures coverage of a pasted job description with BM25 term weights.
A dependency-free CLI that scaffolds a runbook from a project's own package.json and checks READMEs and runbooks by their real headings, with a score and a CI gate.