7z Secure WorkspaceA Windows VS Code extension for opening and editing encrypted
Version 1.0.2 targets Windows x64 and VS Code 1.136.1 or later. The stable 1.0 baseline was regression-tested on VS Code 1.136.1. Current capabilities
Opening an archiveOpen a local The extension prompts for the archive password and then asks which session mode
to use. The Command Palette entry Session modesThe selected mode is immutable for the archive session. Changing mode requires closing and reopening the archive. Secure VirtualUses a virtual archive filesystem and a private This minimizes VS Code working-copy exposure, but it is not a complete sandbox. Plaintext exists in process memory while being used, and protection against page files, process dumps, clipboard use, malicious software, or every possible observation path available to another VS Code extension is outside the guarantee. Standard VirtualUses the virtual archive filesystem with normal VS Code MaterializedExplicitly writes plaintext into a random extension-owned system-TEMP working directory for normal filesystem, Git, and external-tool workflows. Filesystem changes are autosynced back to the encrypted archive, and manual Sync remains available as an explicit checkpoint. New sessions use a directory of the form:
The archive filename is intentionally not included in the TEMP directory name.
Materialized change detection uses a per-session keyed content baseline instead of re-reading every archive member on every sync. After a successful archive commit, every file written by that sync is read back from the committed archive and verified before its new baseline is accepted. Verification cost therefore scales with the current write set rather than with unrelated files already in the archive. Materialized mode treats the real working directory as the source of truth. An
operation such as rename may be represented as archive
Successful normal close performs a final sync before deleting plaintext. If the final sync fails, the working directory is retained for recovery rather than risking data loss. Crash/force-kill cleanup cannot be guaranteed, and deletion is not secure erase. Use Secure Virtual or Standard Virtual when archive-native item identity and metadata fidelity matter more than normal filesystem/tooling compatibility. Zero-byte files and Data EncryptionA zero-byte 7z member has no file-data stream, so per-file Data Encryption is not applicable while it remains empty.
Header Encryption edge casesHeader Encryption protects archive member names, including directory names. Directory-only archives are supported. A truly empty archive has no member name to protect, so Header Encryption is reported as N/A instead of pretending that an OFF state is meaningful. The directory-only implementation details and transactional temporary-anchor
rule are documented in VS Code lifecycle
Final lifecycle regression should be performed with an installed VSIX because the Extension Development Host has a debugger-specific workspace-reload lifecycle. Activity Bar UIThe extension contributes a 7z Secure Activity Bar item. Its command surface exposes the session-appropriate operations, including:
Per-file Toggle Data Encryption remains in the Explorer file context menu because that operation requires a selected archive member. InstallationVS Code MarketplaceIn VS Code, open Extensions (
Manual VSIX installationRelease VSIX packages are also available from GitHub Releases. In VS Code use: Extensions → The Marketplace/VSIX package bundles the native bridge and Repository: https://github.com/Nishitox/7z-Secure-Workspace Build from sourceNative bridge changes require Windows x64, CMake, Visual Studio C++ Build Tools, Git, and 7-Zip 26.03 x64:
For JavaScript-only changes, use the included VS Code Extension Development Host configuration. Release packaging is performed with:
The native release build pins bit7z 4.1.0 and targets 7-Zip 26.03. Native binary
hashes are recorded in the generated runtime manifest and verified again during
packaging. Detailed source layout, packaging prerequisites, and release
provenance are documented in Security and supportThe canonical security intent is documented in
The project is maintained on a best-effort basis. No response-time or support SLA is promised. Ordinary reproducible bugs may be reported through GitHub Issues. Documentation
Third-party notices remain in
Project and license
|