🔐 Vylt — Vault/Media Encryption Engine
- Version: v0.1.0
- Author: @ankit-chaubey
- License: Apache-2.0
🧠 Why Vylt Exists
In a world where data privacy is increasingly opaque, Vylt was created from a simple belief:
Your data should never leave your control — not even for encryption.
Vylt is a local-first, offline-only vault encryption system designed for people who:
- do not trust third‑party services with raw data
- want cryptographic guarantees, not marketing promises
- prefer tools that are honest about irreversible security
- complete gallery and folder support with multi-layer encryption.
- all encryption happens directly on your device—zero internet exposure.
- fully secured for protecting your private photos, videos, and personal data.
This project was built originally for personal use and later shared so others can preserve privacy with confidence.
🧱 Security Architecture (3‑Layer Protection)
Vylt uses three distinct cryptographic layers, all executed entirely on your device:
🔐 Layer 1 — Vylt Container Layer
-
Custom archive format (
.vylt) -
Secure header with:
- archive ID
- part number & total parts
- metadata length
- SHA‑256 integrity hashes
-
Optional metadata shielding
🔒 Layer 2 & 3 — ciph secure encryption engine
Powered by ciph (C-based SHA-256/ChaCha20-Poly1305 streaming engine):
- Two internal encryption stages
- Streaming, FD-safe, constant-memory
- No temp plaintext leaks
📌 Important: Each ciph layer itself contains multiple cryptographic rounds. All encryption happens offline — Vylt never connects to the internet.
Projects:
🗄️ Metadata Shield (Optional)
When --seal-meta is enabled:
- File names & folder structure are encrypted separately
- Metadata size becomes variable (stored in header)
- Archive still lists correctly after decrypting metadata
Without shield:
- Metadata remains visible
- Faster listing
- Same data security level
⚠️ CRITICAL SECURITY WARNINGS
🚨 Password Loss = Permanent Data Loss
- If you forget the data password → your files are gone forever
- Metadata password cannot recover encrypted data
- No backdoors. No recovery. No master key.
➡️ Write your password down. Store it safely. Verify twice.
⚠️ Do NOT Rename or Modify .vylt Parts
- Archive ID & part numbering are required for recovery
- Renaming or altering filenames may break multi‑part discovery
⚠️ Threading Guidance
-
Default:
1thread (safe) -
Recommended maximum: 4 threads
-
Using more threads than your system supports may:
- slow encryption
- increase memory pressure
- reduce stability
📦 Installation
pip install vylt
Or editable (development):
pip install -e .
PyPI: https://pypi.org/project/vylt/
🚀 Usage
Encrypt (no metadata shield)
vylt encrypt myfolder
Encrypt with metadata shield
vylt encrypt myfolder --seal-meta
List archive contents
vylt list myfolder.*.vylt
Decrypt archive
vylt decrypt myfolder.*.vylt
🧪 Automated Testing & Integrity
Vylt includes full workflow tests:
- single file
- large files
- nested folders
- shielded & unshielded metadata
- SHA‑256 integrity verification
Tests run via GitHub Actions on every push.
🔧 Configuration
Vylt reads config from:
~/.vylt.json
Example:
{
"threads": 2,
"reuse_data_password_for_meta": true,
"max_password_attempts": 5,
"password_from_env": "VYLT_PASSWORD"
}
This allows CI / workflow automation without prompts.
🧭 Roadmap
Planned future work:
- ☁️ remote cloud sync (encrypted blobs only)
- ⏱️ scheduled backups
- 📱 full‑device encryption mode
- 📚 formal archive specification docs
🧑💻 Author & Developer
-
VYLT — design, format, CLI, orchestration Author: Ankit Chaubey (@ankit-chaubey)
-
Powered By CIPH — cryptographic encryption engine
🌟 Support & Community
If this project helped you:
- ⭐ Star the repo
- 🍴 Fork it
- 🔗 Share with privacy‑conscious friends
If you modify or redistribute:
- follow the Apache‑2.0 license
- keep credit and repository links
📜 License
Apache License 2.0
Copyright © 2026 Ankit Chaubey
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at:
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
⚠️ Disclaimer
This tool uses strong cryptography.
If you forget your password, your data cannot be recovered.
Use responsibly.
This project exists because privacy matters. Your data. Your keys. Your control. 🔏
Metadata
Release files for vylt 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vylt-1.1.1.tar.gz | 19.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vylt-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.3 kB
Release files / vylt-1.1.1.tar.gz
| Download URL | vylt-1.1.1.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90e22d526966c1fbb2ddf86b6f772b2d5e04a7a067aa7e5c852091c7367675f3
|
|
BLAKE2b-256 checksum How to use checksums |
8e4b0005aac12710bcf7cfbd49b837c64f410bce333525ffcef2c6098aa99a4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 8, 2026.
Transparency logRelease files / vylt-1.1.1-py3-none-any.whl
| Download URL | vylt-1.1.1-py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2829575cdd6f0ba15abeab32c1d9b9bc69dfb94a50a567b01c8641ef121926c
|
|
BLAKE2b-256 checksum How to use checksums |
4ae83a5ad1c935e86d761f7c2afdc546b841ef66e8ee0c6189192be7a7682e10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 8, 2026.
Transparency logSecurity for vylt 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for vylt-1.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.