v1.2

Profiles

• `microvault profile [service2 ...]` — define a named, non-secret group of service names.
• `microvault env --profile [--json]` — export only that profile's keys; `--json` batches a whole profile into one password prompt for a calling tool instead of one prompt per key.
• Python API: `vault.profile_services()`, `vault.env_profile()`.

MeXiCOSINT integration

• Fixed stale/incorrect service names in the README's setup guide.
• Documented the new `microvault profile mexicosint ...` step, so MeXiCOSINT only ever sees its own 5 keys instead of the whole vault.

Docs

• New landing page for GitHub Pages (`docs/index.html`).

v1.1

What's New

Package refactor

MicroVault is now a proper Python package instead of a single file:

• core.py — crypto, storage, alias primitives (import-safe, no prompts)
• vault.py — public API module for programmatic access
• cli.py — interactive shell, env export, and the new run command

microvault run — one-liner key injection

Unlock the vault, inject a service key into the environment, and exec a command — all in one step:

microvault run github -- npx -y @modelcontextprotocol/server-github

The key lives only in the child process's environment. Never written to disk, never shown on screen.

Python API module

Import MicroVault from any Python tool:

from microvault import vault
key = vault.get('openai')

No server, no network — reads the same encrypted vault file the CLI uses.

Other

• python -m microvault support
• GitHub alias default updated to GITHUB_PERSONAL_ACCESS_TOKEN for MCP server compatibility
• pyproject.toml: explicit package discovery, v1.1

v1.0

First public release of MicroVault — a local, offline, encrypted CLI vault for API keys.