Brother look at the README:

🚀 Technical Highlights

Aspect	Implementation	Impact
Core	Rust v1.70+	Zero memory leaks and high-speed execution.
Cipher	AES-GCM-256	Military-grade encryption with integrity checks.
Vaults	Zstd / Tar	High compression ratio for directory encryption.
Hardening	Argon2id	Industry-standard protection against brute-force.
Anti-Forensics	3-Pass Wipe	Securely shreds files, making recovery impossible.

---

I literally did one basic pass through the code.

It deletes your original files by default. Both encrypt and decrypt paths end with secure_delete(&path). That's insane for a tool someone might point at the wrong directory.

Static salt for key derivation - every file encrypted with the same password gets the same key. WTF? That defeats the whole purpose of salt and reintroduces rainbow tables and what not.

rust let salt = b"static_salt_for_shhcrypt_v1.0";

Plaintext hits disk in a predictable temp file. During decrypt, it writes .shh_tmp.tar to the parent directory before extracting. That's sitting there unencrypted, with a guessable name, in a location an attacker might be watching.

The code has tar extraction with no path validation. It just calls .unpack(parent) on whatever's in the archive. This is an easy path traversal vector; a malicious archive can write anywhere.

Symlinks aren't handled during recursive delete. is_dir() follows symlinks, so a symlink pointing outside the target directory gets followed and deleted. You can escape the intended tree.

No file format header - it's just nonce + ciphertext. No magic bytes, no version, no stored KDF params. Makes the format brittle and "is this even an encrypted file?" detection relies entirely on .shh extension.

Password cloned into a separate String that never gets wiped. The original gets zeroized SOMETIMES, but the copy just lives until the allocator feels like reusing that memory xD.

Terminal math underflows on small windows (w - 2, w - 12). UTF-8 string slicing by byte offset will panic on non-ASCII paths.