endpoint_vault 0.2.0

Encrypted endpoint failure capture, reliability statistics, and recovery tools for Flutter apps. Capture critical API failures with client-side redaction and encryption.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.2.0 - 2026-08-21

Changed

• BREAKING: The AES-256 encryption key is now always derived from encryptionKey via SHA-256, regardless of length. Previously an exactly-32-character key was used as raw key bytes while any other length was SHA-256 derived. Payloads encrypted with an exactly-32-character key under earlier versions cannot be decrypted after upgrading (all other key lengths are unaffected). encryptionKey no longer needs to be 32 characters — any high-entropy passphrase works.

0.1.1 - 2026-08-18

Fixed

• Forward-compatible error-type mapping for DioExceptionType values added in newer dio releases (fixes analysis against dio 5.11)
• Raised dio lower bound to 5.5.0 (DioMediaType requirement)
• Removed unused connectivity_plus dependency
• Corrected repository URL metadata

0.1.0 - 2026-08-17

Added

• Initial release of EndpointVault Flutter SDK
• EndpointVault client for SDK initialization and event capture
• EndpointVaultInterceptor for automatic Dio request capture
• AES-256 encryption service for payload encryption
• Automatic redaction of sensitive headers and body fields
• Configurable redaction rules with regex pattern support
• Offline queue for storing events when network unavailable
• Device-side replay via the onReplayRequest callback in EndpointVault.init, so replays run through the app's own Dio instance and interceptors
• Extension methods on Dio Options for marking critical requests
• File attachment capture for FormData requests
• Local event storage with retry management and server-driven settings
• Support for custom server URLs (self-hosted deployments)
• Environment and app version tracking for regression analysis
• Event stream for real-time monitoring of captured events

Security

• Client-side encryption before any data leaves the device
• Default redaction of Authorization headers, tokens, and passwords
• Secure key derivation using SHA-256 for non-32-byte keys