AeroFTP

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

Git history includes hundreds of interim commits between releases (fix, feat, refactor, docs). Example: between v2.4.0 and v2.5.0 there are 3 interim commits (ad2626e, 64f8b5b, da1937e) before the release commit.

Repository on GitHub, which uses git. git is distributed.CHANGELOG.md documents all security fixes with CVE references: CVE-2025-54804 (russh DoS, v2.4.0), CVE-2026-25537 (jsonwebtoken, v2.4.0), SEC-001 through SEC-004 (v1.5.0-v1.6.0). v2.5.0 Security section documents 86 audit findings remediated. See https://github.com/axpnet/aeroftp/blob/main/CHANGELOG.md

Each release has a unique SemVer identifier: v2.0.2 through v2.5.0 (20+ releases). Version tracked in 5 files: package.json, tauri.conf.json, Cargo.toml, snapcraft.yaml, splash.html

Every release is identified by an annotated git tag: v2.0.2, v2.0.3, v2.0.5, v2.0.6, v2.0.7, v2.0.8, v2.1.0, v2.1.2, v2.2.0, v2.2.2, v2.2.3, v2.2.4, v2.3.0, v2.4.0, v2.5.0. Tags trigger automated CI/CD builds via GitHub Actions.

Non-trivial release notes file in repository: https://github.com/axpnet/aeroftp/blob/main/CHANGELOG.md.

CHANGELOG.md documents all security fixes with CVE references: CVE-2025-54804 (russh DoS, v2.4.0), CVE-2026-25537 (jsonwebtoken, v2.4.0), SEC-001 through SEC-004 (v1.5.0-v1.6.0). v2.5.0 Security section documents 86 audit findings remediated. See https://github.com/axpnet/aeroftp/blob/main/CHANGELOG.md

GitHub Issues with structured templates: https://github.com/axpnet/aeroftp/issues/new/choose — includes bug_report.md and feature_request.md templates. CONTRIBUTING.md "Reporting Bugs" section with instructions.

GitHub Issues: https://github.com/axpnet/aeroftp/issues

Single-maintainer project with active development (commits daily). CONTRIBUTING.md commits to 7-day bug report acknowledgment. All 22 Dependabot PRs were triaged within minutes of creation (11 closed with rationale, 10 kept open).

Feature requests accepted via GitHub Issues template. CONTRIBUTING.md commits to 14-day PR review. Active development evidenced by 20+ releases in 4 months (v2.0.2 to v2.5.0), each adding user-requested features.

GitHub Issues provides a permanent, publicly searchable archive: https://github.com/axpnet/aeroftp/issues

SECURITY.md published at standard location with full vulnerability reporting process: https://github.com/axpnet/aeroftp/blob/main/SECURITY.md — includes supported versions, reporting instructions, and response commitments.

SECURITY.md directs to GitHub Security Advisories for private reporting: https://github.com/axpnet/aeroftp/security/advisories/new — "Please do not report security vulnerabilities through public GitHub issues."

SECURITY.md and CONTRIBUTING.md both commit to 48-hour initial response for security vulnerabilities, well within the 14-day requirement.

Automated build via Cargo (Rust) + Vite (TypeScript/React) + Tauri 2. CI builds on 3 platforms (Linux, macOS, Windows) via GitHub Actions. Commands: npm run build (frontend), cargo build --release (backend), npm run tauri build (full app).

Uses industry-standard tools: Cargo (Rust), npm (Node.js), Vite (bundler), TypeScript compiler, Tailwind CSS (PostCSS). All widely used in their ecosystems.

All build tools are FLOSS: Rust/Cargo (MIT/Apache-2.0), Node.js/npm (MIT), Vite (MIT), TypeScript (Apache-2.0), Tauri (MIT/Apache-2.0), Tailwind (MIT). No proprietary tools required.

95 Rust unit tests across 15 modules, invocable via cargo test or npm test. Documented in CONTRIBUTING.md Test Requirements section. CI runs tests automatically on every push and PR. See https://github.com/axpnet/aeroftp/blob/main/CONTRIBUTING.md

Standard invocation: cargo test (Rust standard) or npm test (defined in package.json). Both documented in CONTRIBUTING.md.

GitHub Actions CI runs cargo test, cargo clippy, tsc --noEmit, and i18n:validate on every push to main and every pull request. See .github/workflows/build.yml.

CONTRIBUTING.md Test Requirements section: "All pull requests should include tests for new features and bug fixes where applicable. Pull requests that reduce test coverage or break existing tests will not be merged." See https://github.com/axpnet/aeroftp/blob/main/CONTRIBUTING.md

v2.1.0 AeroSync Phase 2 added 12 Rust unit tests for sync journal, SHA-256 checksum, error taxonomy, retry policy, and file verification. v2.4.0 added FTP/SFTP/WebDAV/S3 provider tests. Test maintenance commit cca32aa converted FTP test passwords to SecretBox.

CONTRIBUTING.md Test Requirements section lists 4 specific test commands (cargo test, security:regression, i18n:validate, tsc --noEmit) and states tests should accompany PRs. See https://github.com/axpnet/aeroftp/blob/main/CONTRIBUTING.md

CI runs cargo clippy --all-targets -- -D warnings (all Clippy warnings treated as errors) and tsc --noEmit (TypeScript strict mode with strict: true in tsconfig.json). Security regression suite also runs. See .github/workflows/build.yml

-D warnings flag means any Clippy warning blocks the CI pipeline — code cannot be merged with unresolved warnings. TypeScript strict mode enforces type safety. Evidence: commit fbada09 "Rust warning fixes".

Clippy with -D warnings (deny all) in CI. TypeScript strict: true in tsconfig.json. Security regression script checks for specific dangerous patterns. Not maximally strict (no clippy::pedantic) but substantially strict.

The primary developer has conducted 12+ independent security audits covering OWASP Top 10, XSS prevention, SQL injection, path traversal, command injection, and TOCTOU race conditions.

XSS (escapeHtml chain), SQL injection (parameterized SQLite queries), path traversal (validate_relative_path), command injection (backend shell_execute denylist), zip slip (entry name validation), TOCTOU (Mutex locks). All mitigated with dedicated countermeasures.

All crypto uses publicly published standards: AES-256-GCM-SIV (RFC 8452), AES-256-KW (RFC 3394), AES-SIV, Argon2id (OWASP 2024), HMAC-SHA512, ChaCha20-Poly1305, scrypt (RFC 7914).

Uses only established Rust crypto crates: aes-gcm-siv, chacha20poly1305, aes-siv, aes-kw, scrypt, argon2. No custom/homemade cryptographic implementations.

All cryptographic dependencies are open source under MIT/Apache-2.0 licenses.

AES-256 (256-bit keys), SHA-256/512, Argon2id with 128 MiB memory / t=4 / p=4. All exceed NIST minimum requirements through 2030.

Default security mechanisms use AES-256-GCM-SIV, ChaCha20-Poly1305, Argon2id, HMAC-SHA512. MD5 is only available as a user-facing hash utility in CyberTools, never used as a security mechanism.

No SHA-1 or CBC mode in security mechanisms. Uses authenticated encryption: AES-GCM-SIV (not CBC), AES-SIV, ChaCha20-Poly1305.

Network connections use TLS via rustls (SFTP/FTPS) which supports ephemeral ECDHE key exchange for perfect forward secrecy. Local at-rest encryption (AeroVault) does not involve key agreement protocols (N/A for PFS).

AeroVault master passwords use Argon2id (128 MiB / t=4 / p=4) with per-user random salt. Cryptomator uses scrypt. Both exceed OWASP 2024 recommendations.

All cryptographic keys and nonces are generated using OsRng (OS-level CSPRNG). Password Forge uses CSPRNG. No use of insecure random generators for security purposes.

All distribution via HTTPS: GitHub Releases, npm registry, crates.io, Snap Store. Source code hosted on GitHub (HTTPS/SSH).

GitHub Releases provides SHA checksums for all artifacts. Snap packages are signed by Snapcraft. No artifacts are retrieved over plain HTTP without verification.

No unpatched medium+ vulnerabilities. All findings from 12+ independent security audits have been resolved within days. Dependabot monitors dependencies with weekly checks.

All critical vulnerabilities are fixed immediately — documented across v2.0.x through v2.5.1 changelogs with specific finding IDs (SEC-, CF-, RB-*, etc.).

No credentials in the repository. OAuth tokens stored in OS keyring (keyring crate) or AES-256-GCM encrypted vault. API keys never committed — .gitignore covers .env files. GitHub secret scanning is active.

Clippy (Rust linter) runs on every CI build with -D warnings (deny all warnings). TypeScript strict mode enabled. Both enforced in GitHub Actions before release.

Clippy includes rules for common Rust vulnerabilities (unsafe usage, integer overflow, unwrap on None). Custom security regression script (.github/scripts/security-regression.cjs) checks for command injection denylist and shell_execute patterns on every CI run.

All clippy and static analysis findings are fixed before release. v2.5.1 resolved 254 clippy warnings. All 12+ security audit findings fixed with tracking IDs.

Clippy runs on every push to main and every pull request via GitHub Actions CI. Not just daily — on every single commit.

Rust unit tests (cargo test) run in CI on every build. 12+ independent security audits performed manually before major releases (documented in changelogs).

Rust is memory-safe by default. The project uses minimal unsafe blocks (only for libc::statvfs FFI call), which are documented with SAFETY comments. No C/C++ code in the project.

Rust debug builds have assertions enabled by default (debug_assert!). Cargo test runs with assertions active. Production builds use release profile where panics are caught by Tauri error handling. 12 Rust unit tests validate sync, retry, journal, and error classification logic.

All medium and higher severity vulnerabilities discovered through cargo test and security audits have been fixed promptly. v2.5.1 changelog documents 254 lint fixes, v2.4.0 resolved all 12-auditor findings, v2.2.0 fixed 31 findings across 6 auditors. No outstanding vulnerabilities.