Skip to main content

Repository Vault

RVP creates and restores encrypted Git and directory archives. Python >=3.10, Git and pyzipper are required. CLI: repo-vault or python -m repo_vault. Use explicit --config and --local-config. Archive commands accept --password-file, --archive-root and --restore-root. No personal configuration is bundled.

The existing WinZip AES format is retained. File contents are encrypted; outer member names and sizes remain visible. Use a random strong password and keep it separate from artifacts. Publishing Python code does not hide its implementation.

Embedding applications inject Runtime services with runtime_context. Credential references and local snapshot sources require explicit resolvers. Local-config composition accepts a mapping of relative paths to bytes; restore retains checksum, path, symlink and preserve/backup_replace protections.

Build a wheel, check scripts/check_dist.py and twine check --strict, then run scripts/verify_install.py 0.1.0 with the wheel normally installed outside the source. Only verified synthetic fixtures are permitted. MIT license.

Commands and compatibility

  • pack: bundle, tracked_snapshot, latest_commit or directory_snapshot; configured shortcuts support single inputs and grouped directories/files.
  • unpack: local storage ZIP with -i, or configured browser download; supports strict, force and clean restore modes and extra restore targets.
  • archive / unarchive: encrypted full Git bundle archives, with explicit roots and a password file. Repository metadata and ordinary snapshot DAT formats remain compatible with the original AutoScripts implementation.
  • replace-random, reset-fork: maintain a configured storage repository. Read --help and use a dedicated backup storage repository. Changed directory packs retain the original upstream-reset behavior; this may reset storage history.
  • generate-password -o PATH: creates a random password without overwriting an existing entry. Linux uses restrictive modes; Windows applies a user-only ACL before writing the secret. Password values are never intentionally logged.

Ordinary pack/unpack configuration uses password.file_path or password.command (an argument list). File passwords use the first line. Credential references are opaque application references, not secret values. Without an injected resolver they fail explicitly. Password command failures do not echo arguments or output.

Global options can precede or follow the subcommand. CLI values override only when explicitly supplied. Explicit local JSON overrides the explicit base JSON. Relative paths follow the current working directory, as in the original implementation. The independent CLI does not discover AutoScripts configuration or home directories. The AutoScripts adapter retains its existing defaults and credential-store selection.

Local snapshot sources belong to embedding applications. Supply a snapshot_loader in Runtime returning a mapping of relative local-config paths to bytes. The package composes committed source with these files and retains the existing checksum metadata format. Restore validates paths, checksums and symlinks before target cleanup; preserve retains existing local files and backup_replace retains comparison copies.

Security limits

The format is standard WinZip AES ZIP with the existing PBKDF2 parameters, not a new cryptographic protocol. A copied DAT permits offline password guesses, so use a random long password. Outer ZIP names and sizes remain visible, including bundle names; the .dat suffix does not conceal the file format. Changing the password file does not re-encrypt existing backups. This release does not perform password rotation.

Only Python code, the license and distribution metadata are allowed in the wheel. Tests use synthetic data and local temporary repositories. No production DAT, password file, personal configuration, credential database, log or publication token is bundled.

Metadata

Release files for estrellio-repo-vault 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for estrellio-repo-vault 0.1.0
File Interpreter ABI Platform Actions
estrellio_repo_vault-0.1.0-py3-none-any.whl Python 3 none any Details for estrellio_repo_vault-0.1.0-py3-none-any.whl

Release files / estrellio_repo_vault-0.1.0-py3-none-any.whl

Download URL estrellio_repo_vault-0.1.0-py3-none-any.whl
Size 34.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e39401dd5106e69a398352b8c7405791bea4261799546a3d09a060bdb7732cec
BLAKE2b-256 checksum
How to use checksums
7302a00bd356027655f38b173737152a77eade0d340e0162f858c552cc9e0222
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for estrellio-repo-vault 0.1.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page