Repository navigation
Releases: DANVERSE01/reference-vault
Releases · DANVERSE01/reference-vault
Release list
Reference Vault 1.0.0 — Your references, organized locally
Reference Vault 1.0.0
A local visual-reference library for Windows and independent Android: paste a public portfolio URL, retain published originals and context, and browse organized project folders offline.
Downloads
- Windows x64: extract the ZIP and run
ReferenceVault.exe. Windows 10/11 with Edge/WebView2. No Python installation is required. - Android: install the universal APK (Android 7+, ARM64/ARMv7/x86/x86_64). Downloads run on the phone. Use Export folder to preserve a copy outside app storage before uninstalling.
- Verify files against
SHA256SUMS.txt. Native artifact provenance and upstream sources/notices accompany the release.
Included
- Behance project/profile/collection extraction, public Wix CMS, rendered portfolio pages and direct media.
- Per-project originals, published text and credits, offline HTML, JSON/CSV inventories and SHA-256 hashes.
- Persistent queue, pause/resume, guarded retries and explicit coverage/failure reporting.
- DANVERSE night identity, restrained motion, English default and persistent Arabic text switching with English layout geometry.
- Local processing without an account, extraction subscription or cloud upload.
Verified and limited
- Windows: a real Behance project saved 18 files; the frozen diagnostics passed all seven checks. Native launch, folder selection and language persistence were tested after a bridge-exposure defect was fixed.
- Physical OPPO / Android 11: independent extraction, image/video validation and system-folder export verified. A Behance sample saved 16 images; two Vimeo embeds returned HTTP 401 and remained explicitly failed.
- Android 7+ and four ABIs are build targets, not a claim of testing every phone. Other devices and 16KB page-size environments are not physically validated.
- Source restrictions, unavailable originals and unknown crawl totals are reported. The initial Windows build is not Authenticode signed. Native dependency provenance is recorded; byte-for-byte reproducibility of upstream native runtimes is not claimed.
See validation, coverage and build instructions.