grantry 0.1.0__tar.gz

grantry-0.1.0/.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    groups:
+      python-dependencies:
+        patterns:
+          - "*"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

grantry-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,29 @@
+name: ci
+on:
+  push:
+    branches: [main]
+  pull_request:
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python: ["3.10", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+      - name: Set up Python
+        run: uv python install ${{ matrix.python }}
+      - name: Sync
+        run: uv sync --all-extras --dev
+      - name: Ruff
+        run: uv run ruff check .
+      - name: Ruff format check
+        run: uv run ruff format --check .
+      - name: Mypy
+        run: uv run mypy
+      - name: Pytest
+        run: uv run pytest -q

grantry-0.1.0/.github/workflows/codeql.yml

@@ -0,0 +1,23 @@
+name: codeql
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: "0 6 * * 1"
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      actions: read
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v3
+        with:
+          languages: python
+      - name: Analyze
+        uses: github/codeql-action/analyze@v3

grantry-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,20 @@
+name: publish
+on:
+  release:
+    types: [published]
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      # Trusted Publishing: PyPI trusts this workflow via OIDC, so no API token
+      # is stored anywhere.
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+      - name: Build sdist and wheel
+        run: uv build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

grantry-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.pyc
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+dist/
+uv.lock
+dist/

grantry-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing to grantry
+
+Thanks for your interest. grantry is a small, focused tool, and contributions
+are welcome.
+
+## Ground rules
+
+- grantry stays local first. No feature should add a server, telemetry, or a
+  network call to anything other than the cloud provider itself.
+- Secrets belong in the OS keychain. Never write a secret to a file or a log.
+- Product code is fully typed and passes `mypy` in strict mode.
+- Every change ships with a test. Network facing code is tested against a fake
+  server, never against a real account.
+- Prose and comments use plain English and no em dashes.
+
+## Getting set up
+
+grantry uses [uv](https://docs.astral.sh/uv/).
+
+```bash
+git clone https://github.com/saimeda32/grantry
+cd grantry
+uv sync --all-extras --dev
+```
+
+## The checks
+
+Run all of these before opening a pull request. CI runs the same on macOS,
+Linux, and Windows across Python 3.10 and 3.14.
+
+```bash
+uv run ruff check .
+uv run ruff format --check .
+uv run mypy
+uv run pytest -q
+```
+
+## Workflow
+
+1. Fork the repository and create a branch with a clear name, for example
+   `feat/azure-provider` or `fix/refresh-race`.
+2. Write a failing test, then the code to make it pass.
+3. Keep the change focused. One idea per pull request.
+4. Make sure the checks above pass.
+5. Open a pull request and describe what changed and why.
+
+## Adding a cloud provider
+
+A provider lives in `src/grantry/providers/` and implements the small `Provider`
+protocol in `providers/base.py`: `name`, `start_login`, `refresh`,
+`list_identities`, and `mint`. Nothing outside the provider package should
+import a cloud SDK. Add a fake server under `tests/fakes/` and test the login
+and mint flow end to end against it.
+
+## Reporting bugs
+
+Open an issue with the command you ran, what you expected, and what happened.
+Never paste real credentials or tokens.

grantry-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

grantry-0.1.0/PKG-INFO

@@ -0,0 +1,212 @@
+Metadata-Version: 2.4
+Name: grantry
+Version: 0.1.0
+Summary: Local credential broker for humans and AI agents, AWS-first
+Author: Sai Kiran Meda
+License: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: botocore>=1.43
+Requires-Dist: keyring>=25.7
+Requires-Dist: mcp>=1.28
+Requires-Dist: pyyaml>=6.0.3
+Description-Content-Type: text/markdown
+
+# grantry
+
+**A local credential broker for humans and AI agents. AWS first.**
+
+grantry logs you into AWS IAM Identity Center once, then hands out short lived
+credentials on demand. You get a clean command line. Your AI coding agents get
+the same credentials over MCP, but only for the accounts and roles you allow,
+only for as long as you permit, and every request is written to an audit log.
+
+Everything stays on your machine. grantry talks to AWS and nothing else. No
+account, no server, no telemetry. Tokens live in the OS keychain, never in a
+plain file, and no secret is ever written to a log.
+
+[![CI](https://github.com/saimeda32/grantry/actions/workflows/ci.yml/badge.svg)](https://github.com/saimeda32/grantry/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Python](https://img.shields.io/badge/python-3.10%2B-blue.svg)](pyproject.toml)
+
+---
+
+## Why grantry exists
+
+Every other credential tool assumes a person is at the keyboard. But agents are
+now heavy users of cloud credentials, and they are bad at logging in. They
+cannot click a device flow link, and they stall when a session expires. The
+common workaround is pasting long lived keys into the agent's environment.
+Those keys never expire and are never audited. That is a real security problem.
+
+grantry removes the workaround. The agent asks, grantry checks your rules, and
+hands over short lived credentials or a clear refusal. You keep one login, one
+policy, and one audit trail across every agent on your machine.
+
+## Install
+
+Once grantry is published to PyPI:
+
+```bash
+uvx grantry --help        # run without installing
+# or
+pipx install grantry
+```
+
+Until then, install from source:
+
+```bash
+git clone https://github.com/saimeda32/grantry
+cd grantry
+uv sync
+uv run grantry --help
+```
+
+Works on macOS, Linux, and Windows. Python 3.10 or newer.
+
+## Quick start
+
+```bash
+# 1. Point grantry at your Identity Center, just once. It remembers.
+grantry --start-url https://your-org.awsapps.com/start --region us-east-1 login
+
+# 2. Generate a starter policy from your real access.
+grantry init
+
+# 3. See what you can reach.
+grantry ls
+
+# 4. Run any command as a role.
+grantry run my-dev/AWSReadOnlyAccess -- aws s3 ls
+```
+
+After `grantry login`, the native `aws` CLI, boto3, and Terraform work too. Run
+`grantry populate` once to create the matching profiles in `~/.aws/config`, then
+use `aws --profile ...` with no grantry in the loop.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `grantry login` | Log in to Identity Center once, for all accounts and roles. |
+| `grantry ls` | List the account and role identities you can use. |
+| `grantry run <id> -- <cmd>` | Run a command as a chosen identity. |
+| `grantry switch <id>` | Print shell exports so `eval "$(grantry switch <id>)"` adopts an identity. |
+| `grantry populate` | Write `~/.aws/config` profiles for your access. Adds, updates, and prunes only its own profiles. |
+| `grantry check` | Diagnose your session and access, with clear exit codes. |
+| `grantry init` | Generate a working policy from your real access. |
+| `grantry audit` | Print the grant history, or write an HTML timeline with `--visualize`. |
+| `grantry graph` | Write an HTML map of what your agents can reach under the policy. |
+| `grantry mcp` | Run grantry as an MCP server for agents. |
+| `grantry install [client]` | Add grantry to an AI client's MCP config. Auto detects all if none named. |
+| `grantry admin assignments --as <id>` | Crawl who has what across the whole org. Admin only. |
+| `grantry logout` | Clear the saved session for the current instance. |
+| `grantry instances` / `grantry use <name>` | List remembered orgs, or switch between them. |
+| `grantry install` / `grantry uninstall` | Add or remove grantry from an AI client's MCP config. |
+| `grantry version` | Print the version. |
+
+## Use it with your AI agents
+
+One command wires grantry into your AI clients:
+
+```bash
+grantry install            # auto detect every client you have
+grantry install cursor     # or a specific one
+grantry install --dry-run  # preview without writing
+```
+
+Supported: `claude-code`, `claude-desktop`, `cursor`, `windsurf`, `vscode`.
+grantry is added without touching your other MCP servers, and each client gets
+its own audit label. Restart the client to load it.
+
+The agent then has four tools: `whoami`, `list_identities`,
+`get_credentials(identity, ttl)`, and `check_access(identity)`. If no one is
+logged in, the agent can call `request_login`, which notifies you and waits for
+your approval, then resumes on its own.
+
+## Policy
+
+Write `~/.grantry/policy.yaml`, or let `grantry init` generate it from your real
+access. See [examples/policy.yaml](examples/policy.yaml).
+
+```yaml
+agents:
+  allow:
+    - identity: "*/AWSReadOnlyAccess"
+    - identity: "dev-*/AWSPowerUserAccess"
+  deny:
+    - identity: "*prod*/*Admin*"
+  max_ttl: 15m
+humans:
+  max_ttl: 12h
+```
+
+Three rules govern it:
+
+1. A deny always beats an allow.
+2. For agents, anything not allowed is refused. Safe by default.
+3. For you, anything not mentioned is allowed.
+
+An identity is `account-name/role-name`, and `*` is a wildcard, so
+`dev-*/AWSReadOnlyAccess` means read only in any account whose name starts with
+`dev`.
+
+A note on TTL and AWS: grantry cannot shorten an SSO credential below the
+lifetime AWS issues it with, because the reserved SSO roles do not allow client
+side re assumption. grantry reports the real AWS expiration and adds an advisory
+when a credential outlives your policy cap. The real control for short sessions
+is the permission set session duration, set by an admin in IAM Identity Center.
+
+## Admin: see who has what across the org
+
+```bash
+grantry admin assignments --as your-mgmt/AWSAdministratorAccess --visualize
+```
+
+This crawls the whole organization and writes an interactive graph of
+principals, permission sets, and accounts, with the links between them. It is
+safe to offer because AWS is the gatekeeper: only an identity that can assume a
+management or delegated admin role gets any data. The crawl caches principal
+names and uses retry hardening, so it handles organizations with thousands of
+assignments.
+
+## How your data is stored
+
+grantry uses no database. It is a single user local tool.
+
+- **Secrets** (SSO tokens) live in the OS keychain, through `keyring`.
+- **State** lives as plain files in `~/.grantry/`: `instance.json`,
+  `policy.yaml`, and an append only `audit.jsonl` (mode 0600).
+- **Interop**: `grantry login` also writes the AWS CLI token cache in
+  `~/.aws/sso/cache/`, the same file `aws sso login` writes, so the native
+  tools work.
+
+Everything survives reboots. To remove grantry state: `grantry logout` and
+`rm -rf ~/.grantry`.
+
+## Security
+
+- Secrets live only in the OS keychain. Redaction happens in one place, so no
+  log line can leak a token.
+- The MCP server is not a network service. It talks to the agent that started
+  it over stdio.
+- Credentials are short lived and scoped to what the policy allows.
+- Every grant is recorded in `~/.grantry/audit.jsonl`, and never includes the
+  credentials themselves.
+
+See [SECURITY.md](SECURITY.md) to report a vulnerability.
+
+## Roadmap
+
+grantry v1 covers AWS Identity Center. The provider layer is written so Azure
+and GCP can be added without touching the engine, policy, audit, or MCP
+surface. Team mode (shared, signed policy) comes after that.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). In short: fork, branch, write a test,
+keep `ruff`, `mypy`, and `pytest` green, open a pull request.
+
+## License
+
+[Apache 2.0](LICENSE).