| Version | Supported |
|---|---|
| 1.x.x | ✅ Yes |
| < 1.0 | ❌ No |
We take security seriously. If you discover a security vulnerability, please report it responsibly:
Do not open a public issue for security vulnerabilities.
Instead, email: abdullah.pkg.ctg@gmail.com
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes
We will:
- Acknowledge receipt within 48 hours
- Provide a timeline for fix
- Credit you in the security advisory (if desired)
- Downloads files using aria2, curl, or git
- Verifies checksums when provided
- Uses HTTPS with certificate validation (always enabled)
- Applies git/npm/pip configuration optimizations
- ❌ Execute downloaded files automatically
- ❌ Disable SSL verification for speed
- ❌ Store credentials or tokens
- ❌ Phone home or collect telemetry
- ❌ Modify system files outside documented config
-
Always verify checksums when downloading from untrusted sources:
aria2c --checksum=sha256=abc123... -o file.zip https://example.com/file.zip
-
Use trusted sources — fast-download assumes HTTPS from known hosts
-
Keep aria2 updated — security fixes in aria2 benefit you:
# Windows winget upgrade aria2.aria2 # macOS brew upgrade aria2 # Linux apt upgrade aria2 # or dnf/pacman
-
Review agent configs before installing — they define download behavior
- aria2's Metalink/BitTorrent support could download from untrusted peers if Metalink files are compromised
- Git shallow clones don't verify commit signatures (use full clone for verification)
- Rate-limited servers may cause aria2 to fallback to curl (expected behavior)
Security patches will be released as patch versions (e.g., 1.0.1) and announced via:
- GitHub Security Advisories
- Release notes
- Repository discussions
Security contact: Abdullah Al Hadi — abdullah.pkg.ctg@gmail.com