keynest 0.0.1__tar.gz

keynest-0.0.1/.gitignore

@@ -0,0 +1,220 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+junit.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+.idea

keynest-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Matthew Martin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

keynest-0.0.1/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.4
+Name: keynest
+Version: 0.0.1
+Summary: Developer secret workbench: a pure-Python keystore with GUI and CLI for OS keyring and AWS Secrets Manager
+Project-URL: Repository, https://github.com/matthewdeanmartin/keynest
+Project-URL: Documentation, https://keynest.readthedocs.io/en/latest/
+Project-URL: Changelog, https://github.com/matthewdeanmartin/keynest/blob/main/CHANGELOG.md
+Project-URL: homepage, https://github.com/matthewdeanmartin/keynest
+Project-URL: issues, https://github.com/matthewdeanmartin/keynest/issues/
+Author-email: Matthew Martin <matthewdeanmartin@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: aws,cli,credentials,developer-tools,gui,keyring,secrets,secrets-manager,tkinter,vault
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.11
+Requires-Dist: boto3>=1.34.0
+Requires-Dist: keyring>=24.0.0
+Description-Content-Type: text/markdown
+
+# keynest
+
+Developer keystore that is pipx-installable and supports the OS keychain / credential
+manager and AWS Secrets Manager — with both a CLI and a Tkinter GUI.
+
+keynest is a **developer secret workbench**. It helps a single developer stop scattering
+secrets across Notepad, stray `.env` files, shell history, and repo-adjacent config. It
+manages *secret maps* (JSON dictionaries of keys to values) in either the laptop OS secret
+store (via Python [`keyring`](https://pypi.org/project/keyring/)) or
+[AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) (via `boto3`).
+
+The guiding opinion: **make the safe path the easy path.** Instead of
+
+```bash
+export DATABASE_PASSWORD=...
+```
+
+prefer
+
+```bash
+keynest run my-app -- python app.py
+```
+
+See [spec/spec.md](spec/spec.md) for the full product specification.
+
+## Prior Art
+
+[aws-vault](https://github.com/ByteNess/aws-vault) is the best prior art and is recommended
+over this tool for the moment. The main advantage of keynest will be that it is pure Python
+and ships a GUI. keynest also borrows patterns shamelessly from `chamber`, SOPS, KeePassXC,
+and the developer-docs-as-a-feature approach of Infisical / Doppler / 1Password.
+
+## Installation
+
+```bash
+pipx install keynest
+```
+
+Or with pip:
+
+```bash
+pip install keynest
+```
+
+## Usage
+
+```bash
+keynest --help
+```
+
+> Note: keynest is in early development. The CLI and GUI described in the
+> [spec](spec/spec.md) are not yet implemented — the package scaffold and quality gates
+> are in place first.
+
+## Contributing
+
+See [CONTRIBUTING.md](docs/extending/CONTRIBUTING.md).
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md).
+
+## Current implementation
+
+The implementation has moved beyond the early scaffold note above: both the CLI and Tkinter GUI are available, with
+OS-keyring and AWS Secrets Manager backends. The specification remains useful as product history, while the
+[user documentation](docs/index.md) describes the behavior and limitations of the current code.
+
+The preferred installation is an isolated global tool environment:
+
+```bash
+uv tool install keynest
+```
+
+or:
+
+```bash
+pipx install keynest
+```
+
+The install provides `keynest` and `keynest-gui`. Start with:
+
+```bash
+keynest health
+keynest --help
+keynest-gui
+```
+
+The recommended usage path injects a map only into a child process:
+
+```bash
+keynest run my-app/dev -- python app.py
+```
+
+See the [documentation home](docs/index.md), [concepts and storage](docs/concepts.md), dedicated
+[CLI reference](docs/usage/cli.md), [GUI guide](docs/usage/gui.md), [AWS guide](docs/aws.md), and
+[security model](docs/security.md).
+
+On Windows, keynest does not enumerate Credential Manager. It uses Python `keyring` to request exact entries under
+its own `DeveloperSecretWorkbench` service and keeps a separate non-secret index for listing. Windows itself has a
+credential-enumeration API, but keynest does not call it; this is an implementation boundary, not protection from
+other software running as your user. Consequently, unrelated credentials stored by other applications do not appear
+in keynest. The [storage documentation](docs/concepts.md#why-keynest-cannot-see-your-other-windows-credentials) has the
+full explanation.

keynest-0.0.1/README.md

@@ -0,0 +1,108 @@
+# keynest
+
+Developer keystore that is pipx-installable and supports the OS keychain / credential
+manager and AWS Secrets Manager — with both a CLI and a Tkinter GUI.
+
+keynest is a **developer secret workbench**. It helps a single developer stop scattering
+secrets across Notepad, stray `.env` files, shell history, and repo-adjacent config. It
+manages *secret maps* (JSON dictionaries of keys to values) in either the laptop OS secret
+store (via Python [`keyring`](https://pypi.org/project/keyring/)) or
+[AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) (via `boto3`).
+
+The guiding opinion: **make the safe path the easy path.** Instead of
+
+```bash
+export DATABASE_PASSWORD=...
+```
+
+prefer
+
+```bash
+keynest run my-app -- python app.py
+```
+
+See [spec/spec.md](spec/spec.md) for the full product specification.
+
+## Prior Art
+
+[aws-vault](https://github.com/ByteNess/aws-vault) is the best prior art and is recommended
+over this tool for the moment. The main advantage of keynest will be that it is pure Python
+and ships a GUI. keynest also borrows patterns shamelessly from `chamber`, SOPS, KeePassXC,
+and the developer-docs-as-a-feature approach of Infisical / Doppler / 1Password.
+
+## Installation
+
+```bash
+pipx install keynest
+```
+
+Or with pip:
+
+```bash
+pip install keynest
+```
+
+## Usage
+
+```bash
+keynest --help
+```
+
+> Note: keynest is in early development. The CLI and GUI described in the
+> [spec](spec/spec.md) are not yet implemented — the package scaffold and quality gates
+> are in place first.
+
+## Contributing
+
+See [CONTRIBUTING.md](docs/extending/CONTRIBUTING.md).
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md).
+
+## Current implementation
+
+The implementation has moved beyond the early scaffold note above: both the CLI and Tkinter GUI are available, with
+OS-keyring and AWS Secrets Manager backends. The specification remains useful as product history, while the
+[user documentation](docs/index.md) describes the behavior and limitations of the current code.
+
+The preferred installation is an isolated global tool environment:
+
+```bash
+uv tool install keynest
+```
+
+or:
+
+```bash
+pipx install keynest
+```
+
+The install provides `keynest` and `keynest-gui`. Start with:
+
+```bash
+keynest health
+keynest --help
+keynest-gui
+```
+
+The recommended usage path injects a map only into a child process:
+
+```bash
+keynest run my-app/dev -- python app.py
+```
+
+See the [documentation home](docs/index.md), [concepts and storage](docs/concepts.md), dedicated
+[CLI reference](docs/usage/cli.md), [GUI guide](docs/usage/gui.md), [AWS guide](docs/aws.md), and
+[security model](docs/security.md).
+
+On Windows, keynest does not enumerate Credential Manager. It uses Python `keyring` to request exact entries under
+its own `DeveloperSecretWorkbench` service and keeps a separate non-secret index for listing. Windows itself has a
+credential-enumeration API, but keynest does not call it; this is an implementation boundary, not protection from
+other software running as your user. Consequently, unrelated credentials stored by other applications do not appear
+in keynest. The [storage documentation](docs/concepts.md#why-keynest-cannot-see-your-other-windows-credentials) has the
+full explanation.

keynest-0.0.1/keynest/__about__.py

@@ -0,0 +1,38 @@
+"""Metadata for keynest."""
+
+__all__ = [
+    "__credits__",
+    "__dependencies__",
+    "__description__",
+    "__keywords__",
+    "__license__",
+    "__readme__",
+    "__requires_python__",
+    "__status__",
+    "__title__",
+    "__version__",
+]
+
+__title__ = "keynest"
+__version__ = "0.0.1"
+__description__ = (
+    "Developer secret workbench: a pure-Python keystore with GUI and CLI for OS keyring and AWS Secrets Manager"
+)
+__readme__ = "README.md"
+__credits__ = [{"name": "Matthew Martin", "email": "matthewdeanmartin@gmail.com"}]
+__keywords__ = [
+    "secrets",
+    "keyring",
+    "aws",
+    "secrets-manager",
+    "credentials",
+    "vault",
+    "developer-tools",
+    "cli",
+    "gui",
+    "tkinter",
+]
+__license__ = "MIT"
+__requires_python__ = ">=3.11"
+__status__ = "3 - Alpha"
+__dependencies__ = ["keyring>=24.0.0", "boto3>=1.34.0"]

keynest-0.0.1/keynest/__init__.py

@@ -0,0 +1,5 @@
+"""Developer secret workbench: a pure-Python keystore with GUI and CLI for OS keyring and AWS Secrets Manager."""
+
+from keynest.__about__ import __version__
+
+__all__ = ["__version__"]

keynest-0.0.1/keynest/__main__.py

@@ -0,0 +1,6 @@
+"""Allows `python -m keynest` invocation."""
+
+from keynest.cli import main
+
+if __name__ == "__main__":
+    raise SystemExit(main())

keynest-0.0.1/keynest/app.py

@@ -0,0 +1,24 @@
+"""Tkinter application entry point for keynest.
+
+Launch with ``python -m keynest.app`` or the ``keynest-gui`` console script.
+"""
+
+from __future__ import annotations
+
+import sys
+
+
+def main() -> int:
+    """Launch the keynest GUI, returning a process exit code."""
+    try:
+        # Imported lazily so the CLI works even where tkinter is unavailable.
+        from keynest.ui.main_window import run  # pylint: disable=import-outside-toplevel
+    except ImportError as exc:  # pragma: no cover - tkinter missing on some builds
+        print(f"Could not start the GUI (is tkinter installed?): {exc}", file=sys.stderr)
+        return 1
+    run()
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

keynest-0.0.1/keynest/backends/__init__.py

@@ -0,0 +1 @@
+"""Storage backends for secret maps."""