Skip to content

Changelog — HeelonVault

All notable changes are documented here, in descending version order. Format inspired by Keep a Changelog.


  • Task-based user guides rewritten in French and English, clarifying recovery, backups and edition boundaries.
  • Bilingual screenshots regenerated from production widgets with synthetic data; obsolete images removed. Isolated generation, image provenance and hashes, lightweight CI validation and pre-release freshness checks.
  • Password editor: the “password field is empty by default” hint appears only while editing with current-password prefilling disabled in the profile; it is absent when that option is enabled and when creating a secret.

  • Deep-teal primary actions, rounded corners and subtle elevation; light bordered secondary actions, softly tinted utility controls on hover and red destructive actions. Sign-in, PIN unlock and release notifications share the same visual language; pills remain for selectors.

  • Popovers use a single bordered, elevated panel without repeated frames around nested layout boxes. Spaced menu rows, subtle separators, visible keyboard focus and destructive colors preserved on hover.

  • Secret cards no longer move on hover, and border widths stay constant, including on selection: titles and actions no longer shift. More legible copy controls.

  • Lighter view/sort selectors: a quiet shared surface and a light active option with a teal underline, distinct from hover. GTK components, bundled icons and logical dimensions retained for Linux, Windows and macOS.

  • Native GTK tests cover rest/hover/press/focus/disabled states, stable geometry and compact windows, with optional captures for visual and HiDPI validation.

  • Fixed contextual-control contrast: dark connected-identity text on a light header button, white editor back text on teal and white delete text on red. Label and icon contrast checked across interactive states.

  • Arrow keys and editing shortcuts are no longer intercepted by the secret list while focus is in search or another field (editor, notes, profile, password, numeric setting). A previously selected card can no longer redirect Ctrl+C to copying a secret.
  • Ctrl+F (Cmd+F on macOS) selects the existing search text. Enter immediately applies the current text and focuses the first visible result; without results, focus stays in search. Card navigation is limited to visible results, with translated keyboard guidance and native GTK regression tests.
  • Automatic background analysis at sign-in and after PIN unlock, then after secret, trash, import, vault and team-access changes made in the application. The badge no longer requires opening the center.
  • Explicit states: updating, affected-item count, zero only after a complete analysis without findings, unavailable report or error/incomplete coverage. Translated tooltips; a missing report is never presented as healthy.
  • Closely spaced requests are coalesced; viewing the latest report avoids redundant analysis. Leaving the page no longer cancels the calculation; locking/signing out cancels queued or running analyses and prevents late results.
  • Native GTK tests with real SQLite cover off-page analysis, creation/deletion/restoration, coalescing, navigation, incomplete reports, errors and locking.
  • Optional background discovery of stable releases from the official GitHub repository at startup, at most once every 24 hours. No request before consent, which is stored per operating-system user; manual checking remains available with automatic checks disabled.
  • Nonblocking HeelonVault-branded banner for initial consent, release notes/downloads and deferral. Dedicated Profile & Security panel with installed version, progress and explicit offline/configuration-error states, in French and English.
  • No automatic download or installation and no vault, account or license data sent. Bounded network time and response size, redirects rejected and links restricted to the official repository. Release discovery does not attest package authenticity or security.
  • Tests cover semver comparison, consent, persistence, HTTP errors, size limits, network deadlines and native GTK flows with simulated results.
  • Windows: the application no longer crashes when a sensitive copy expires (password after 20 s, recovery phrase after 60 s), nor when locking during the countdown. The clipboard is now emptied with no format at all instead of receiving an empty text, which GTK converted by dereferencing a null pointer.
  • PDF audit report (Professional edition): the heelonvault password opens the document again. Since 2.0.0 its encryption combined SHA-256 with a format that mandates MD5, so no PDF reader could open it. It now uses standard AES-256 encryption (PDF 2.0), with the same editing restrictions.
  • Fixed RUSTSEC-2026-0381, 0382, 0383 and 0385 in both lockfiles: ctutils 0.4.5, rustls-webpki 0.103.16, webpki-root-certs and webpki-roots 1.0.11. The fixes address constant-time operations and rejection of distrusted emSign certificate chains; no advisories ignored.
  • Refreshed compatible dependencies, including Tokio 1.54.1, UUID 1.29.0, ICU 2.4.0 and webbrowser 1.2.5; migrated the rstest test dependency to 0.28.0.
  • crypto-common 0.1.7 requires generic-array 0.14.7 on the legacy branch used by SQLx. matchit remains at 0.8.4, the exact version required by Axum; no upstream constraints bypassed.
  • Security lint pass (cargo clippy-secure) clean and enforced in CI: tests and the build script no longer use unwrap, expect or panic!, and fail with a contextual error instead. The remaining exceptions are limited to third-party macro expansions (#[tokio::test], static_loader!) and documented in place.
  • Aligned the Core, App, URL checker and Premium versions. Updated the SBOM and license inventory.
  • No changes to the public API, database schema, encrypted formats, backups or signed reports. Minimum Rust version unchanged.

  • Added a Community security center with local cross-vault analysis, grouped password reuse, shared strength diagnostics, expiration within 30 days, invalid data and URL warnings. Results distinguish affected items from findings and expose incomplete coverage.
  • Added a native GTK page with metric filters, vault selection, prioritized expandable findings and progressive display in batches of 50. Opening an item rechecks vault access; returning from the editor refreshes diagnostics.
  • The shared zxcvbn-based estimator now drives stored-password diagnostics and the strength widget. API tokens, SSH keys and documents are excluded from password strength/reuse checks. Master-password acceptance policy is unchanged.
  • The editor assesses URL syntax/protocol locally. Each optional online DNS/TLS check requires explicit consent and connects only to a validated public host, without sending paths, queries, credentials or HTTP requests. Certificate validation is not a site-safety verdict; no reputation provider is enabled.
  • Added the internal, unpublished heelonvault-url-check crate. Core remains network-free. No database migration, encrypted payload or backup format changes; public Core additions are semver-additive.
  • Added diagnostic, real SQLite permission/revocation, TLS fixture and native GTK smoke tests. Locking cancels analysis, invalidates pending results and clears the editor/diagnostic view.
  • Security fix. Without a Professional license, an administrator could open user and team management from the profile (the sidebar did check the license). Rights now come from a single source (edition from the license × role): the Users and Teams pages are no longer built without a license, and the Premium services themselves refuse access-granting operations. Revocations remain possible.
  • Fix. Changing the master password trimmed leading and trailing spaces, unlike the login screen: a password ending with a space could become impossible to type. Passwords are now used as typed, and the 16-character minimum is checked before submitting.
  • Redesigned page: one column read top to bottom, one row per setting. “Account protection” header (2FA, PIN, automatic lock), then Account, Sign-in and protection, Session, Preferences, Data and Administration. One primary button per action; complex actions expand in place.
  • Language applied as soon as it is selected; current password only asked for when the email address changes; “Never” for automatic lock confirmed before it is applied; .hvb export only shown to administrators, the only ones allowed to use it.
  • On the Community edition, an administrator sees what the Professional license adds, with no action leading to those features.
  • Fixed the first-run wizard hint: “12 characters and 4 categories, or 14 characters and 3 categories”.
  • Refined visual identity: one palette built around the HeelonVault teal, distinct semantic colours (success, warning, danger, info) and a consistent corner-radius scale. Warnings no longer use the brand colour.
  • Depth and finish: soft two-layer shadows on cards and panels, short hover transitions, focus ring shown for keyboard navigation only.
  • Bundled HeelonVault icon set: identical rendering on Linux, Windows and macOS whatever the system theme.
  • Sidebar: the active entry is marked with an accent bar; the “Security center” entry shows an icon, the number of items to review and a “New” pill until first opened. Selection follows the brand colour instead of the system accent.
  • Security center: shield coloured by the state of the last analysis, metric cards with icon and counter, findings with icon and severity chips. List badges use the same scale (“Weak” in red, “Duplicate” in amber).
  • French texts fully accented and proofread.

Not released separately: these fixes ship with 2.1.0. No changes to the public API, database schema or backup formats.

  • Pinned the development and release toolchain to Rust 1.99.1 in both repositories. The minimum supported Rust version remains 1.98; CI separately checks compilation of all targets and features under 1.98.0.
  • Updated rustls to 0.23.46 and quinn-proto to 0.11.19 in both Cargo graphs: fixes RUSTSEC-2026-0338, 0340, 0343 and 0346 through 0349 without advisory exclusions.
  • Updated compatible dependencies, then migrated BIP39 from 2.2.2 to 3.0.0. Known vectors and an encrypted backup with its verifier, captured before migration, protect compatibility with existing recovery phrases. No backup format or public API changes.
  • CI: refreshed GitHub actions and tools; audits of both lockfiles, all-feature Premium checks and supply-chain warnings treated as errors. Checks use native tools rather than a container requiring its own Rust installation.
  • Regenerated the SBOM and verified reproducibility; the plan and results are documented internally.
  • Transactional update: the new version is prepared in /opt/heelonvault.new, then swapped with the current install; any error after the swap automatically restores the previous version. System dependencies are installed before anything is modified.
  • Stale binaries are refused (version different from the sources or older than a source file changed since the build); the most recent binary between target/release and the repository root is used, HEELONVAULT_BINARY points to another one (useful with CARGO_TARGET_DIR).
  • Updating while HeelonVault is open is refused.
  • Consistent backups (sqlite3 .backup) with an integrity check, instead of a raw file copy; sqlite3 added to the Ubuntu/Debian dependencies.
  • The current profile (Personal or Enterprise) is offered as the default; installed and new versions are shown (/opt/heelonvault/VERSION file).
  • heelonvault --version prints the version and exits without starting the application.

Patch release: no change to the public API of heelonvault-core nor to the database schema.

  • Linux AppImage: the database and logs were created in data/ and logs/ under the launch directory (with the development-mode database name, heelonvault-rust-dev.db). The launcher now uses ~/.local/share/heelonvault/heelonvault-rust.db and ~/.local/state/heelonvault/logs/, like the system install. On first launch, a database created by the 2.0.0 AppImage (launch directory or home directory) is copied to the new location; the original is kept.
  • Secret types (Password, API token, SSH key, Secure document) were displayed as a technical key (secret-type-…) in the list and the trash: the translations were missing.
  • Every UI text now goes through the FR/EN translation catalogs: trust console and “Certify & Export” menu, signed audit report messages, password strength meter, Pro Santé Connect sign-in, license badge and seal, empty list states, editor, CSV import preview, PIN badge, shared vault roles. They follow language changes without a restart, including the license badge and the certification menu.
  • The license badge is no longer passed around as text and parsed back to find the customer name: it is rendered in the active language at display time.
  • New tests: the FR and EN catalogs define the same keys, and every key used by the UI exists in both.
  • heelonvault-premium is declared proprietary (LicenseRef-Heelonys-Proprietary) instead of Apache-2.0, which shows in the SBOM and the third-party license inventory. Its source can be opened for reading to a customer’s security teams for audit, under a non-disclosure agreement; the documentation says so.
  • New user-facing “Installation and quickstart” guide (MSI, DMG and AppImage packages, SHA-256 verification, first launch, data location, license, uninstall). The former developer content moved to docs/internal/DEVELOPMENT*.md.
  • Maintainer-only documentation (development, release, Windows packaging, CI plan, specifications, graphic guidelines, manual QA) is grouped under docs/internal/, which is not published on the documentation site.
  • Update guide rewritten (package updates, Linux system install, rollback, migration from the Python version). Architecture, security, README and contribution guide aligned with the current code; version numbers removed from documents.
  • User guide screenshots display again (docs/images/user-guide/).
  • Signed SBOM link fixed: it is published on the GitHub releases.
  • Premium page and guides: Pro Santé Connect sign-in is described as in development (identity is verified, linking to a local account is not available yet).
  • Removed: scripts/run.sh (superseded by the launcher generated by the system install and by scripts/run-dev.sh), the top-level tests/ directory (stale copies of tests living in crates/, never compiled), scripts/create-github-issues-1.1.0.sh, and the never-used LicenseStatusWidget module.

Stable release. It follows the 1.2.0-rc.1 pre-release, includes all of its content, plus the changes below. The version moves to 2.0.0 because the public API of the heelonvault-core crate published on crates.io is no longer compatible with 1.1.0 (see “Breaking changes”); the product, the crate and heelonvault-premium share the same version number.

Security — the UI no longer keeps any plaintext secret

Section titled “Security — the UI no longer keeps any plaintext secret”
  • The secret list no longer keeps decrypted passwords in memory. Previously every refresh decrypted the whole vault and kept plaintext values (Strings never wiped) in the display data and in each card’s copy handler for the whole session.
  • On load, each value is decrypted only long enough to compute the strength verdict and a SHA-256 fingerprint for duplicate detection, inside the loader thread; the plaintext stays in a SecretBox (wiped on drop) and fingerprints never leave that thread. Only booleans (has_secret, is_weak, is_duplicate) reach the UI.
  • On-demand copy: copying a password (button or Ctrl+C) re-opens the vault (open_vault_for_user, so access is re-checked: a revoked share can no longer be copied), decrypts that single secret, copies it, then wipes it. The button is disabled during the operation (double-click guard, keyboard included); a message is shown when the session is locked or the copy fails.
  • The master key copy handed to the loader is now wiped (Zeroizing).
  • Clipboard exposure indicator in the header bar: a clipboard icon inside an amber ring that burns down over the actual clearing delay (20 s for a password or login, 60 s for the recovery phrase). The tooltip says what is exposed (password, login, recovery phrase) and the countdown; when idle: “No secret exposed by HeelonVault”. Clicking clears the clipboard at once. The indicator never claims that no secret is in memory.
  • A lock (manual, automatic or logout) happening while an on-demand copy is being decrypted no longer sends the password to the clipboard afterwards: the session is checked again once decryption is over, and the “Session locked” message is shown.
  • When another application replaces the clipboard, the sensitive value held by HeelonVault is wiped at once instead of at the end of the delay.
  • Switching between card and list views rebuilds the widgets from the last load (metadata only): no query, no decryption, no “Loading” screen. Usage counters bumped since the load are kept.

UX — list view, first launch and online help

Section titled “UX — list view, first launch and online help”
  • Card or list view: two buttons in the list status bar switch between the card grid and a compact list with aligned columns (type, title, login, domain, key badges, quick actions). Filtering, sorting, search, counters and keyboard shortcuts are unchanged; switching is instant (no reload). The choice is persisted in ui_view_preferences.json (installation-wide preference).
  • First launch: after the bootstrap wizard, the application returns to the sign-in screen instead of quitting; the new username is pre-filled and “Account created, please sign in.” is displayed. No session is opened implicitly: the account key produced by the bootstrap is wiped from memory.
  • Online help: “?” button in the header bar opening https://doc.heelonvault.heelonys.fr (tooltip translated FR/EN).
  • Secret cards: login and domain on two lines with icons.
  • Bootstrap: closing the wizard after a successful initialization was treated as a cancellation and quit the application (state flag not shared with the close_request handler).
  • The active sort button is highlighted again (the vault-secret-sort-button-active CSS class was never applied).
  • Cards: in English, weak passwords were shown with the green “strong” badge (colour derived from the French label). Strength is now a boolean, translated only for display; “Health”, “Incomplete”, “Shared” badges and quick-action tooltips are translated FR/EN.

Breaking changes — heelonvault-core crate API

Section titled “Breaking changes — heelonvault-core crate API”

Reported by cargo-semver-checks against 1.1.0 as published on crates.io. They only affect code using the crate; the application and existing databases are not affected (no migration since 1.2.0-rc.1).

  • Removed: admin_service::bootstrap_first_admin, user_service::{MasterKeyRotationPolicy, MasterKeyRotationRequest, MasterKeyRotationReport, RotationValidationMode}; methods BackupService::{export_backup, import_backup} and UserService::rotate_master_key_hardened removed or changed.
  • New required methods on public traits: UserRepository (recovery phrase envelope and verifier), VaultRepository::create_vault_with_envelope, SecretService::{record_viewed, record_field_copy}, UserService::{upgrade_legacy_credentials, account_needs_recovery_key}, BackupService::{build_recovery_verifier, verify_recovery_phrase}.
  • BackupApplicationServiceImpl::new takes one more parameter; BootstrapResult gains the recovery_phrase field.
  • New variants: AuditAction::{SecretViewed, SecretPasswordCopied, SecretFieldCopied}, AppError::{Recovery, SingleAccountVault}.
  • AppError, AccessDeniedReason, RecoveryFailure and AuditAction are now #[non_exhaustive]: a match outside the crate needs a _ arm. In return, adding a variant is no longer a breaking change.
  • CI: cargo-semver-checks compares the heelonvault-core API with the latest version published on crates.io and fails when a break is not paired with a major version.
  • CI: cargo publish --dry-run -p heelonvault-core checks that the crate builds on its own, outside the workspace.
  • release_consistency test: heelonvault-core, heelonvault-app and heelonvault-premium must carry the same version, and premium must depend on that version of heelonvault-core.
  • Release procedure documented in RELEASING.en.md.

Release note: v1.1.0 (and v1.1.0-rc.1) is frozen. Changes below are scoped for v1.2.0.

Infrastructure — MSRV Rust 1.96 → 1.98

Section titled “Infrastructure — MSRV Rust 1.96 → 1.98”
  • Aligned rust-version to 1.98 across all 4 workspace members (heelonvault-core, heelonvault-app, sqlx-shim, heelonvault-premium).
  • Confirmed rust-toolchain.toml (core and premium) at 1.98.0.
  • Synced documentation (README FR/EN, Windows packaging runbook) to Rust 1.98.
  • crossbeam-epoch 0.9.18 → 0.9.20: fixes RUSTSEC-2026-0204 (invalid pointer dereference in fmt::Pointer).
  • webbrowser 1.2.1 → 1.2.4: fixes RUSTSEC-2026-0257 (Unix BROWSER argument injection) — relevant to the PSC flow’s browser launch.
  • event-listener 5.4.1 → 5.4.2: fixes RUSTSEC-2026-0221 (!Send tag leak via StackSlot).
  • chacha20 0.10.0 → 0.10.2 and spin 0.9.8 → 0.9.9: replaced yanked versions.
  • cargo audit: 0 vulnerabilities, 0 warnings (previously 2 vulnerabilities + 3 allowed warnings). cargo deny check advisories: ok.

Infrastructure — Edition 2024 and Rust 1.96

Section titled “Infrastructure — Edition 2024 and Rust 1.96”
  • Migrated workspace crates to edition = "2024".
  • Aligned rust-version to 1.96 for heelonvault-core, heelonvault-app, and sqlx-shim.
  • Added rust-toolchain.toml (1.96.0) to keep local and CI build/lint environments consistent.
  • Applied Rust 2024 compatibility hardening: replaced premium test-time std::env::*_var mutation patterns with explicit configuration wiring (no global environment mutation).
  • Reached zero clippy warnings with 1.96 under -D warnings across core/premium scope.
  • Updated Cargo.lock dependencies to latest Rust 1.96-compatible versions.
  • Updated the git reference of heelonvault-premium consumed by the core app.
  • Supply-chain validation preserved: cargo audit (exit 0) and cargo deny check advisories (ok).

Linux installation — migration hardening

Section titled “Linux installation — migration hardening”
  • scripts/install-core.sh now validates the copied migrations payload in /opt/heelonvault/migrations: .sql filename parity plus file-by-file content parity.
  • Generated run.sh now exports HEELONVAULT_MIGRATIONS_DIR=/opt/heelonvault/migrations to enforce a stable production migration path.
  • Installation now fails fast if the migrations directory is missing or empty.

Infrastructure — Open Core polyrepo split (Phase 5f)

Section titled “Infrastructure — Open Core polyrepo split (Phase 5f)”
  • heelonvault-core v1.1.0 published to crates.io: the core library is now a public, reusable artifact.
  • heelonvault-premium extracted into a separate private repository (ppaperso/HeelonVault-Premium): premium code is no longer exposed in the public repository.
  • heelonvault-app references premium as an optional git dependency; the community build (cargo check --workspace) never fetches the private repo.
  • Cargo.toml (workspace root): local patches configured for joint development (no network required locally).
  • VSCode workspace updated to multi-root mode (HeelonVault + HeelonVault-Premium).

Infrastructure — SQLx 0.8 → 0.9 upgrade and RSA elimination (Phase 5e)

Section titled “Infrastructure — SQLx 0.8 → 0.9 upgrade and RSA elimination (Phase 5e)”
  • sqlx dependency updated from 0.8 to 0.9 in heelonvault-core and sqlx-shim (API-compatible, no application code changes).
  • RUSTSEC-2023-0071 eliminated: the rsa crate (timing side-channel on PKCS#1 v1.5 decryption) was a transitive dependency of sqlx 0.8; it is no longer present in the dependency tree.
  • cargo audit: 0 active vulnerabilities (431 dependencies scanned).
  • rust-version = "1.95" aligned across all 4 workspace members (heelonvault-core, heelonvault-app, heelonvault-premium, sqlx-shim).
  • Stable toolchain updated to 1.95.0 (rustc 59807616e, 2026-04-14).
  • No new Clippy lints introduced by 1.95.0.

Dashboard UX — cards and keyboard productivity

Section titled “Dashboard UX — cards and keyboard productivity”
  • Secret cards now follow a clearer mouse/keyboard flow:
    • single click = select,
    • double click = open editor.
  • Removed edit/delete controls from cards to reduce visual noise; maintenance actions now go through dedicated screens.
  • Card ordering is now usage-driven (usage_count descending) to prioritize frequently used secrets.
  • Added/refined card badges: strength, incomplete, duplicate, usage.
  • Global shortcuts on the active card: Ctrl+C (copy secret), Ctrl+L (copy login), Ctrl+U (open URL).
Section titled “Health-related secrets — manual marker and local detection”
  • Added persistent “Health data access” marker in the create/edit form.
  • Added high-confidence local auto-detection to classify relevant health secrets without user configuration.
  • Added quick search shortcut #sante to target marked/detected health secrets.
  • Added a “Sante” badge on matching cards for faster visual identification.

PIN status badge and session countdown timer

Section titled “PIN status badge and session countdown timer”
  • Added a clickable “PIN active” badge in the title bar, kept in real-time sync with the PIN cache state.
  • Three progressive visual states based on remaining session time:
    • Nominal (> 2 h): standard semi-transparent white badge.
    • Warning (≤ 2 h, > 15 min): amber border and text — visual cue that session renewal is advisable.
    • Critical (≤ 15 min): amber-filled badge, text changes to “PIN · Xm”, 2-second pulse animation.
  • Permanent tooltip on the badge: “PIN-secured session — Expires in Xh Ym”.
  • 60-second GLib timer managed by an inner closure (glib::timeout_add_local): cleanly cancelled via SourceId::remove() on every exit path (logout, cache exhaustion, quit).
  • Hermetic lifecycle: badge and timer are reset immediately on every exit path; double-remove is prevented by setting SourceId to None before returning Break.
  • Added PinCache::remaining(hard_timeout) -> Duration method (returns ZERO if already expired).
  • Fix: badge text was unreadable against the dark title-bar background (CSS rules for headerbar button.header-pin-badge label).
  • Fix: badge remained “PIN active” after automatic cache expiry (synced via on_pin_state_cb).
  • Fix: missing “Quit application” button on the PIN unlock dialog.
  • FR/EN localization: new key pin-tooltip-secure.
  • New pin_cache_service: in-memory master-key cache protected by Argon2id (8 MiB, t=3) + AES-256-GCM, never persisted to disk.
  • pin_setup_dialog: PIN activation and deactivation from the user profile view (4–8 digits).
  • pin_unlock_dialog: PIN entry dialog displayed when the auto-lock fires.
  • Auto-lock integration: a logout now triggers a PIN lock (when a PIN is set) instead of a full disconnect, preserving the session in memory.
  • Security: 3 attempts maximum per cache, 12-hour hard timeout, user_id binding (prevents cross-session replay), random AES-GCM nonce per activation, zeroize wipe on Drop.
  • Full FR/EN localization for all PIN messages (entry, error, limit, timeout, enable/disable).

Memory hardening — master key lifecycle (memory PR #1)

Section titled “Memory hardening — master key lifecycle (memory PR #1)”
  • try_pin_unlock now returns Zeroizing<Vec<u8>>: the zeroize guarantee is enforced by the type system.
  • on_unlocked callback redesigned as Option<Zeroizing<Vec<u8>>>: Some(key) on success, None on cache exhaustion — eliminates the Vec::new() sentinel-value idiom.
  • Removed the key.to_vec() in try_pin_unlock that silently stripped the zeroize guarantee.
  • user_service: hardened rotate_master_key_hardened flow enabled with pre/post rotation validation.
  • Owner/shared vault key-envelope rewrap now applied through an atomic SQL mutation.
  • Sample-secret validation is wired into VaultAndSampleSecret mode.
  • Manual verification confirmed: master key change succeeds in real application runtime.
  • Automated verification confirmed: broad cargo test run is green.
  • profile_view: redesigned CSV import into a 3-step user flow:
    • file preview (detected/importable/manual-review rows),
    • visible progress during import,
    • final detailed summary including rows that require manual follow-up.
  • import_service: switched to row-level fault tolerance with a structured summary report (imported, failed, per-row details) instead of one opaque global failure.
  • ui/dialogs/import_progress_dialog: new dedicated import progress dialog.
  • Full FR/EN localization for new import messages (preview, progress, summary, error details).
  • Added scripts/export-legacy-v0.4-to-csv.py to export legacy databases to a CSV format compatible with v1.1 import.
  • Supports legacy layouts via --profile, --workspace-uuid, or explicit --db-path + --salt-path.

v1.1.0 technical debt (issues #5, #6, #7, #8, #9)

Section titled “v1.1.0 technical debt (issues #5, #6, #7, #8, #9)”
  • main: moved env::set_var("GSK_RENDERER", "gl") before Tokio runtime initialization.
  • import_service: removed the global clippy::disallowed_methods bypass and hardened CSV parsing (explicit required-field extraction with typed validation errors).
  • main: split orchestration into focused units (startup flags, runtime/UI execution, service builders) to reduce complexity and duplication.
  • team_service: decomposed share_vault_with_team and rotate_vault_key into internal helpers (member-key resolution, share persistence, audit recording).
  • Added/completed /// docs on public service traits (vault_service, secret_service) to clarify preconditions, error paths, and security contracts.
  • Automated validation run after refactor: cargo test --workspace and cargo clippy --workspace --all-targets -- -D warnings.

Search UX — multi-vault toggle and premium help popover

Section titled “Search UX — multi-vault toggle and premium help popover”
  • shell.rs: added MultiVault toggle button to the left of the search bar; replaces the previous auto-detection mode-switch.
  • Fix: removed selectable(true) from the help popover label — it blocked focus return to the main window after a right-click (apparent freeze).
  • Fix: parse_search_terms — field: value syntax (space after colon) now behaves identically to field:value.
  • Redesigned help (?) popover: three structured sections (caption-heading + dim-label + monospace), help-browser-symbolic icon, fixed 348 px width, autohide(true).
  • Refactor: ContentShell struct with a centralized refresh_i18n closure; new_body.inc delegates all shell i18n updates through a single call.
  • Structured FR/EN i18n keys: main-search-help-no-prefix-title, main-search-help-no-prefix-body, main-search-help-prefix-title, main-search-help-fields, main-search-help-examples, main-search-help-fuzzy.
  • Updated the transitive TLS chain in Cargo.lock: rustls-webpki 0.103.10 -> 0.103.13, rustls 0.23.37 -> 0.23.40.
  • Lockfile verification: vulnerable rustls-webpki 0.103.10 is no longer present.
  • Post-fix validation executed: cargo check, cargo test --locked --all-targets --no-run, cargo clippy --all-targets --all-features -- -D warnings.
  • Expected security impact: fixes the high Dependabot alert and the two related low alerts for rustls-webpki once pushed to main.
  • Hardened password change flow: old/new password comparison now uses constant-time equality in auth_service.
  • Hardened login failure accounting: invalid passwords now correctly increment auth_policy.failed_attempts in the login path.
  • Added server-side TOTP replay guard: a code that was already accepted cannot be reused immediately in the same time window.
  • Added progressive retry backoff in auth_policy_service (bounded exponential growth), complementing the existing lock window behavior.
  • Added security limits for CSV import: max file size, max row count, and max field length.
  • Added strict URL validation for import: only http:// and https:// schemes are accepted.
  • Backup exports (.bak and .hvb) now apply owner-only permissions (0600 on Unix).
  • Restored SQLite files now apply owner-only permissions (0600 on Unix).
  • Added unit tests for:
    • identical password change rejection,
    • CSV URL validation,
    • auth policy backoff calculations.
  • Full validation run completed: cargo test passes after changes.
  • Fixed the rand Dependabot advisory path: removed vulnerable rand 0.8.5 from the resolved graph and pinned rand 0.9.3.
  • Migrated BIP39 recovery-key generation to explicit getrandom entropy, without relying on bip39/rand feature wiring.
  • Moved off the sqlx aggregator crate to a SQLite-only shim (crates/sqlx-shim) to remove unnecessary sqlx-mysql / sqlx-postgres transitive dependencies from lockfile and SBOM.
  • Productionized CycloneDX 1.4 SBOM flow: local generator scripts/generate-sbom.sh, CI freshness gate (check-sbom), and release publication job (generate-sbom-artifact).
  • Release now publishes sbom.cyclonedx.json + sbom.cyclonedx.json.sha256 with build provenance attestation (actions/attest-build-provenance@v4).
  • Harmonized Linux/Windows/macOS release jobs with checksums and GitHub Release uploads via gh CLI.
  • Fixed macOS .app/.dmg packaging path issues (GDK-Pixbuf staging, Homebrew symlink resolution, DMG checksum via shasum -a 256).
  • Added explicit gdk-pixbuf Homebrew dependency in macOS CI/release workflows.
  • Removed remaining Node 20 deprecation warnings by dropping Homebrew caching step based on actions/cache@v4 in macOS jobs.
  • Updated README.md / README.en.md to 1.0.4 and documented signed SBOM publication.
  • Realigned THIRD_PARTY_LICENSES.md and sbom.cyclonedx.json with the final dependency graph.
  • Finalized the split of large Rust screens into dedicated modules for login_dialog, main_window, profile_view, and related flows.
  • Kept the maintainability constraint satisfied: no active UI Rust file above 800 lines.
  • Extracted sizing helpers and UI subcomponents to reduce local coupling and clarify responsibilities.
  • Removed unreferenced intermediate split files left behind during the refactor.
  • Verified that assets/images/user-guide images remain documentation-only assets and are not unintentionally bundled at runtime.
  • Validated the release state with cargo check, cargo clippy, cargo test, and cargo fmt --all -- --check.
  • Bumped application and documentation version to 1.0.3.
  • Added a bilingual user guide (docs/USER_GUIDE.md and docs/USER_GUIDE.en.md) with an end-user manual tone.
  • Integrated real UI screenshots across screen-by-screen sections (bootstrap, login, dashboard, secret creation forms, profile/security, import/export, user/team administration, trash).
  • Structured the guide with a table of contents and formal screen/capture numbering.
  • Added a shared smoke test (scripts/smoke-test.sh) with --install/--remove, permissions checks, and desktop-entry validation.
  • Hardened CI/Release workflows: Rust cache, Fedora container job, external .sha256 checksum asset, build provenance attestation, and core script inclusion in dist/.
  • Bumped application and documentation version to 1.0.1.
  • Official move to 1.0.0 (stable release), removing the beta suffix from the application version and reference documentation.
  • Simplified premium visual header: removed the gold framed panel.
  • New black primary title: REGISTRE DE TRAÇABILITÉ DES ACCÈS.
  • Signed audit log exported as an actionable table (date, action, actor, target, detail).
  • Actor identity resolution now prefers display name / username in exports.
  • Audit targets enriched with vault names and secret titles when available.
  • secret.created event now includes secret title in audit detail payload.
  • Switched from proprietary Source-Available license to Apache 2.0: free to use, modify, and redistribute; HEELONYS copyright and brand retained.

Application license system (LicenseService)

Section titled “Application license system (LicenseService)”
  • Ed25519 signature verification for signed license files (~/.config/heelonvault/license.hvl in dev, /etc/heelonvault/license.hvl in prod).
  • JSON format with payload field (JSON object or serialized string) and signature (128-char hex or base64).
  • Automatic fallback to Community license when no file is present or verification fails.
  • Automatic tolerance of whitespace and 0x prefix in hex values (sanitize_hex_input).
  • Audit log entries LicenseCheckSuccess / LicenseCheckFailure at application startup.
  • “Licence free” / “Licence pro — CLIENT” badge in the login hero section, visible before authentication.
  • License badge in the main-window header bar (next to the BETA badge).
  • High-visibility CSS style .login-license-badge (teal gradient).
  • i18n keys license-status-community, license-status-professional, license-status-invalid added in FR and EN.

  • Security dashboard window rendered via WebKitGTK (WebView-first, no GTK fallback blocks).
  • Global vault score computed in real time with zxcvbn evaluation.
  • Dedicated FR and EN translations for all dashboard labels and states.
  • Each successful login is recorded in the login_history table (migration 0007).
  • History displayed in the Profile & Security view.
  • Guided TOTP activation via QR code in Profile & Security.
  • Mandatory first-code verification before activation is confirmed.
  • TOTP secret stored encrypted in the database (migration 0009).
  • Secret restore from trash: atomic transaction with automatic parent vault restore when needed (avoids “invisible secret” state).
  • Vault resolution fixed in the multi-vault secret edit dialog.
  • Password envelope persistence corrected on reload.

  • Login language selector replaced with FR/EN flags.
  • Fixed a UI freeze during language switching on the login screen.
  • Harmonized live i18n refresh across main-window global areas (sidebar, tooltips, placeholders, stack titles).
  • User language preference now persists and applies live from Profile & Security.
  • Installer hardened with explicit validation of critical artifacts (run.sh, desktop entries).
  • Dual desktop-entry installation (com.heelonvault.rust.desktop and heelonvault.desktop) for environment compatibility.
  • Installer smoke test added to the release workflow.
  • Dedicated CI pipeline (.github/workflows/ci.yml): formatting, lint, build, test compilation, desktop validation, smoke test.

Bootstrap wizard, recovery key, and secure backup

Section titled “Bootstrap wizard, recovery key, and secure backup”
  • 3-step first-admin setup wizard in the login dialog: identity → oath (24-word phrase) → pending.
  • 24-word BIP39-style mnemonic phrase generated at bootstrap via BackupService::generate_recovery_key().
  • Mandatory spot-check of 2 randomly drawn words before confirmation.
  • Clipboard copy with automatic wipe after 60 seconds.
  • Recovery key re-export available from Profile & Security for any admin.
  • BackupApplicationService: RBAC access control on .hvb export and import operations.
  • Audit log introduced (table audit_log, migration 0013).
  • Fixed team vault sharing: member key now derived from password_envelope when no explicit key is provided.
  • Fail-fast protection: explicit failure when no member receives a vault key.
  • Explicit vault picker added to the team sharing dialog.
  • ADMIN badge in the header next to the connected identity.
  • Owner-side shared-state visibility for owned vaults.
  • FR badge labels normalized to uppercase.
  • i18n cleanup: removed obsolete main-vault-shared-badge key.
  • FR/EN coverage across all operational Markdown documentation.
  • Central bilingual documentation index in docs/README.md.

  • Full migration from Python to Rust (GTK4 + libadwaita).
  • Service/repository/model layer in Rust with sqlx and 9 initial migrations.
  • Argon2id authentication, AES-256-GCM encryption, TOTP RFC 6238.
  • Multi-user with isolated vaults per user.
  • Multi-field search with Unicode normalization.
  • Rotating structured JSON logs via tracing.
  • Security Clippy policy (clippy.toml) forbidding unwrap()/expect() on sensitive paths.