-
Notifications
You must be signed in to change notification settings - Fork 0
fun facts
These notes pair with By the numbers for metrics and Lore for the release timeline.
The first commit on 2026-06-17 added only LICENSE, but executable project code that still survives also dates to 2026-06-17. The oldest surviving source-like files include scripts/check-release-metadata.mjs, scripts/build_apt_repository.py, and scripts/validate_linux_package_metadata.py.
The current Rust core followed on 2026-06-18, with durable files such as crates/csv-anonymizer-core/src/service.rs, crates/csv-anonymizer-core/src/types.rs, and crates/csv-anonymizer-core/src/csv_io.rs.
From 2026-06-17 through 2026-07-01, the repository moved from v1.0.1 to v1.0.63. That cadence helps explain why package metadata, changelog entries, workflow checks, and installer scripts show up so prominently in the churn numbers.
On 2026-07-01, docs/code-quality-assessment-2026-07-01.md reported no TODO, FIXME, or HACK markers under frontend/src. That is a small but useful signal for a frontend that manages privacy-sensitive workflow state.
The longest source files on 2026-07-01 cluster around contracts, workflow styling, packaging, and the core service boundary:
| Path | Lines |
|---|---|
crates/csv-anonymizer-core/src/types.rs |
957 |
frontend/src/styles/controls.css |
906 |
frontend/src/styles/data.css |
841 |
scripts/build_apt_repository.py |
662 |
scripts/validate_linux_package_metadata.py |
647 |
crates/csv-anonymizer-core/src/service.rs |
606 |
The list is a compact map of the app's pressure points: typed privacy/report contracts, dense desktop UI states, release packaging, Linux metadata, and the Rust service that ties detection, preview, and anonymization together.
The release/ directory contains old packaged Electron artifacts. For 2026-07-01 source metrics, release/ should be excluded along with generated outputs, otherwise historical packaged bundles would overwhelm the active Rust/Tauri/React source picture.