teamspend-cli 0.2.1__tar.gz

teamspend_cli-0.2.1/.gitignore

@@ -0,0 +1,8 @@
+.venv/
+.venv-freshinstall/
+dist/
+build/
+*.egg-info/
+__pycache__/
+*.pyc
+.pytest_cache/

teamspend_cli-0.2.1/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 2026 Rudrendu Paul and Sourav Nandy
+
+   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.

teamspend_cli-0.2.1/PKG-INFO

@@ -0,0 +1,386 @@
+Metadata-Version: 2.4
+Name: teamspend-cli
+Version: 0.2.1
+Summary: Compare AI coding tool spend before and after a migration -- Cursor, Claude Code, GitHub Copilot, OpenCode, and Codex CLI, real numbers pulled from each vendor's own API or local logs, one command, zero runtime dependencies.
+Project-URL: Homepage, https://github.com/RudrenduPaul/teamspend
+Project-URL: Repository, https://github.com/RudrenduPaul/teamspend
+Project-URL: Bug Tracker, https://github.com/RudrenduPaul/teamspend/issues
+Project-URL: Changelog, https://github.com/RudrenduPaul/teamspend/blob/main/CHANGELOG.md
+Project-URL: Documentation, https://github.com/RudrenduPaul/teamspend/blob/main/docs/getting-started.md
+Project-URL: Author - Rudrendu Paul, https://github.com/RudrenduPaul
+Project-URL: Author - Sourav Nandy, https://github.com/Sourav-nandy-ai
+Author: Rudrendu Paul, Sourav Nandy
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai-coding-agents,claude-code,cli,codex,cost,cost-tracking,cursor,finops,github-copilot,opencode
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business :: Financial
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Utilities
+Requires-Python: >=3.9
+Provides-Extra: dev
+Requires-Dist: build<2,>=1.0; extra == 'dev'
+Requires-Dist: pytest<9,>=7.0; extra == 'dev'
+Requires-Dist: twine<7,>=5.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# teamspend (Python)
+
+Compare AI coding tool spend before and after a migration -- Cursor,
+Claude Code, GitHub Copilot, OpenCode, and Codex CLI, real numbers pulled
+from each vendor's own API or local logs, one command.
+
+[![PyPI version](https://img.shields.io/pypi/v/teamspend.svg)](https://pypi.org/project/teamspend/)
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/RudrenduPaul/teamspend/blob/main/LICENSE)
+[![Python versions](https://img.shields.io/pypi/pyversions/teamspend.svg)](https://pypi.org/project/teamspend/)
+[![npm version](https://img.shields.io/npm/v/teamspend-cli.svg)](https://www.npmjs.com/package/teamspend-cli)
+
+## Why this exists
+
+More teams are running more than one AI coding tool at once, or moving
+between them, than ever before. Cursor's Admin API reports Cursor spend.
+Anthropic's Claude Enterprise Analytics API reports Claude Code spend.
+Neither has a reason to show a competitor's number next to its own, so a
+team mid-migration is left opening two dashboards and doing the
+subtraction by hand. teamspend pulls both sides through the same
+normalized schema and prints one honest delta. This package is the Python
+distribution -- a genuine, independent port, not a wrapper around the
+Node binary.
+
+## Install
+
+```bash
+pip install teamspend
+```
+
+or with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv add teamspend
+```
+
+Zero runtime dependencies: the standard library's `urllib` handles every
+admin-API call. The complementary JS/TS distribution installs the same way
+on the npm side: `npm install -g teamspend-cli` (or `npx teamspend-cli ...`
+to run it once without installing; the older `teamspend` npm name is
+deprecated in favor of `teamspend-cli`, same maintainer and repo) -- see the
+[project README](https://github.com/RudrenduPaul/teamspend#readme) for
+that package. Both distributions (this PyPI package and the npm package)
+are first-class and maintained together.
+
+## Quickstart
+
+```bash
+export TEAMSPEND_CURSOR_TOKEN=<your Cursor Admin API key>
+export TEAMSPEND_CLAUDE_CODE_TOKEN=<your Anthropic Admin/Analytics API key>
+
+teamspend --tools cursor,claude-code \
+  --before 2026-04-01:2026-04-30 \
+  --after 2026-06-01:2026-06-30
+```
+
+Both credentials need org-admin-level access on their platform. If you can
+already see billing for your org, you have what you need.
+
+Output (shape shown below; your real numbers come from your own org's API
+data):
+
+```
+teamspend snapshot -- migration cost comparison
+Tools: cursor -> claude-code
+
+BEFORE (cursor)
+  Total spend:      $2140.00  (exact, usage-based)
+  Active users:      14
+
+AFTER (claude-code)
+  Total spend:      $1860.00  (exact, usage-based)
+  Active users:      14
+
+DELTA: -$280.00 (-13.1%)
+
+Full report: ./teamspend-snapshot-2026-07-16T2031.json
+```
+
+Exit code `0` means both periods fetched successfully, `1` means at least
+one side failed (auth, a vendor API window limit, or a CLI argument
+error) -- see `DATA UNAVAILABLE` in the terminal output and the `error`
+field of the JSON report for the reason.
+
+## GitHub Copilot support
+
+```bash
+export TEAMSPEND_COPILOT_TOKEN=<a token with read:org on the org>
+export TEAMSPEND_COPILOT_ORG=<your GitHub org login>
+export TEAMSPEND_COPILOT_SEAT_PRICE_USD=19   # optional
+
+teamspend --tools cursor,copilot --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30
+```
+
+GitHub's real Copilot usage metrics API has no cost/spend field at all --
+only usage counts, most usefully `ai_credits_used`. teamspend converts that
+to USD at GitHub's own published, fixed rate of 1 AI credit = $0.01 USD,
+and adds `TEAMSPEND_COPILOT_SEAT_PRICE_USD` (if set) once per user for the
+whole window to also reflect the flat per-seat license price GitHub's API
+never exposes. Every Copilot result is therefore always `is_estimated`,
+regardless of whether a seat price was supplied -- see the project
+[README's "GitHub Copilot support" section](https://github.com/RudrenduPaul/teamspend#github-copilot-support)
+and [docs/concepts.md](https://github.com/RudrenduPaul/teamspend/blob/main/docs/concepts.md#copilots-usage-based-report-pagination-and-cost-derivation)
+for the full mechanics.
+
+## OpenCode and Codex CLI: local-only, no API key needed
+
+```bash
+teamspend --tools claude-code,opencode --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30
+teamspend --tools claude-code,codex --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30
+```
+
+Neither [OpenCode](https://github.com/anomalyco/opencode) nor
+[Codex CLI](https://github.com/openai/codex) has an admin, team, or
+billing API -- both are local CLIs, so teamspend reads their own local
+session logs directly off disk instead: `~/.local/share/opencode/storage/message/`
+for OpenCode, `~/.codex/sessions/YYYY/MM/DD/` for Codex. No credential,
+no network call for either. Both results attribute everything to the
+single local user running the command, not a team, and are always marked
+`is_estimated`: OpenCode stores `cost: 0` for most models in its own
+logs, and Codex's local data has no cost field at all, only exact token
+counts. Codex also only keeps roughly the last 7 days of logs readable
+before background-compressing them. See the project README's
+[OpenCode](https://github.com/RudrenduPaul/teamspend#opencode-local-only-no-api-key-needed)
+and [Codex CLI](https://github.com/RudrenduPaul/teamspend#codex-cli-local-only-no-api-key-needed)
+sections for the full mechanics and caveats.
+
+## Personal usage mode, for when you don't have admin access
+
+```bash
+teamspend --tools claude-code-personal,claude-code-personal --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30
+```
+
+If you just want your own personal Claude Code spend and don't have (or
+don't want to use) org-admin access, use `claude-code-personal` instead
+of `claude-code`. It reads Claude Code's own local JSONL session logs
+straight off disk, no API key, no network call, no admin access needed --
+just the logs Claude Code already writes on your machine.
+
+## Session-level cost breakdown
+
+```bash
+teamspend --tools claude-code-personal,claude-code-personal --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30 --breakdown session
+```
+
+Add `--breakdown session` to break a flat total down by session, using
+the `sessionId`/`sessionID` each log entry already carries -- available
+for `claude-code-personal` and `opencode` only, since `cursor`,
+`claude-code`, and `copilot` pull from admin APIs that return per-user
+aggregates with no session field to group by. A session is the most
+honest proxy teamspend can offer for "cost per task" -- it is not a
+measure of whether that session's output was actually good, since no
+vendor exposes that.
+
+## Using the library instead of the CLI
+
+Both packages export a programmatic API for scripts and CI gates that want
+to call teamspend in-process instead of shelling out to a CLI binary.
+
+**TypeScript:**
+
+```ts
+import { fetchCursorSpend, fetchClaudeCodeSpend, buildComparison } from 'teamspend';
+```
+
+**Python:**
+
+```python
+from teamspend import fetch_cursor_spend, fetch_claude_code_spend, build_comparison, DateWindow, PeriodOutcome
+
+before_window = DateWindow("2026-04-01", "2026-04-30")
+after_window = DateWindow("2026-06-01", "2026-06-30")
+
+before_result = fetch_cursor_spend(before_window, cursor_api_key)
+after_result = fetch_claude_code_spend(after_window, claude_api_key)
+
+report = build_comparison(
+    PeriodOutcome("before", "cursor", before_result, None),
+    PeriodOutcome("after", "claude-code", after_result, None),
+)
+print(report.delta_usd, report.delta_percent)
+```
+
+Both return the same shape of normalized data (`total_cost_usd`/
+`totalCostUsd`, `users`, `is_estimated`/`isEstimated`) -- see
+[docs/concepts.md](https://github.com/RudrenduPaul/teamspend/blob/main/docs/concepts.md)
+for the full data model.
+
+## How it works
+
+```
+CLI flags / env vars
+  -> two adapters run concurrently (ThreadPoolExecutor, 2 workers)
+       - Cursor: 30-day-chunk pagination against api.cursor.com/admin/usage, summed per user
+       - Claude Code: single call to api.anthropic.com .../usage_report/claude_code
+                       (guarded: no data before 2026-01-01)
+  -> each field read from a response is validated (require_field) --
+       missing field raises SchemaDriftError, never a silent guess
+  -> suspicious-zero detection: real token/request activity + cost 0
+       -> that user, and the whole side, is marked isEstimated
+  -> build_comparison(): before/after -> delta_usd, delta_percent,
+       top 5 spenders across both periods
+  -> terminal summary + JSON report (0600 file perms) written to cwd
+```
+
+**Concurrency and failure isolation.** `cli.py`'s `run()` submits the
+before and after fetches to a 2-worker `ThreadPoolExecutor` and resolves
+each `Future` independently, catching any exception per side into a
+`PeriodOutcome(result=None, error=...)` rather than letting one side's
+failure abort the other -- mirroring the TypeScript CLI's
+`Promise.allSettled`. Exit code `0` requires both sides to have a
+`result`; either side without one returns exit code `1`.
+
+**Retry/backoff.** Every adapter call goes through `http_client.py`'s
+`fetch_with_retry`, which retries HTTP 429 and 5xx responses up to 3
+times with exponential backoff (0.5s base, doubling), raises
+`AuthenticationError` immediately -- never retried -- on 401/403, and
+raises `RetryExhaustedError` once the retry budget is spent. The real
+network call sits behind a swappable `transport` function (`urllib` in
+production), which is how the pytest suite simulates arbitrary HTTP
+statuses without opening a real socket.
+
+**Cursor pagination.** The Cursor Admin API caps each call's window at 30
+days, so `adapters/cursor.py`'s `_split_into_chunks` breaks any longer
+`--before`/`--after` window into consecutive 30-day chunks, fetches each
+one, and sums the result per `user_id`. If any chunk fails after retries
+are exhausted, the entire fetch fails -- it never reports a total built
+from only the chunks that happened to succeed.
+
+**Claude Code start-date guard.** Anthropic's Claude Enterprise Analytics
+API has no data before 2026-01-01. `adapters/claude_code.py` checks the
+requested window's start date before making any request and raises
+`DataUnavailableError` if it predates that date; the CLI then falls back
+to `--before-csv`/`--after-csv` for that side if one was passed, or
+surfaces the error as that side's `PeriodOutcome.error` otherwise.
+
+**Suspicious-zero detection.** Cursor plans without usage overage, and
+Claude.ai Team/Enterprise seats, report a technically valid `cost_usd`/
+`spend_usd` of exactly 0 for a user who clearly has real token or request
+activity. Both adapters check for that specific combination and mark that
+user -- and the whole side's `is_estimated` flag -- as estimated, so the
+output never shows a misleading exact-looking $0 next to genuine usage.
+
+**The comparison itself.** `compare.py`'s `build_comparison()` takes two
+independently-resolved `PeriodOutcome`s. `delta_usd` and `delta_percent`
+are computed only when both sides have a `result`; otherwise they're
+`None` and the terminal output prints `DELTA: unavailable`. It also
+collects the top 5 spenders from each side, merges and re-sorts them by
+cost, and keeps the top 5 across both periods combined.
+
+## CSV import, for the history a live API can't reach
+
+```bash
+teamspend --tools cursor,claude-code \
+  --before 2025-11-01:2025-11-30 \
+  --after 2026-06-01:2026-06-30 \
+  --before-csv ./before.csv
+```
+
+CSV schema: `date,user_email,cost_usd,is_estimated`, one row per user per
+day. Rows are aggregated per `user_email`.
+
+## Good to know before you run it
+
+- This is a snapshot tool, not a running dashboard. It answers one
+  question well and stops.
+- The output includes real emails and dollar amounts, printed to your
+  terminal and saved to a report file (`0600` permissions, auto-added to
+  `.gitignore`). If you wire this into a scheduled CI job on a public
+  repo, that data lands in your build logs, so check your CI provider's
+  log visibility first.
+- Flat-seat and per-seat billing tiers (Cursor plans without usage
+  overage, Claude.ai Team/Enterprise seats) don't expose true per-user
+  cost through the vendor's own Admin API. When teamspend sees a user
+  with real token or request activity but a reported cost of exactly $0,
+  it marks that user's number, and the whole report, as estimated rather
+  than showing a misleading exact-looking $0.
+- Claude Code's Analytics API has no data before 2026-01-01. A window that
+  starts earlier raises `DataUnavailableError` and, if `--before-csv`/
+  `--after-csv` was passed, falls back to the CSV import path for that
+  side automatically.
+
+## Security
+
+The three admin-API tools need org-admin-level credentials --
+`TEAMSPEND_CURSOR_TOKEN` (Cursor Admin API), `TEAMSPEND_CLAUDE_CODE_TOKEN`
+(Anthropic's Claude Enterprise Analytics API), and/or
+`TEAMSPEND_COPILOT_TOKEN` + `TEAMSPEND_COPILOT_ORG` (GitHub Copilot usage
+metrics API) -- read only from environment variables via `os.environ.get()` in
+`cli.py`'s `_fetch_tool()`. Neither is ever hardcoded, persisted to disk,
+or included in the JSON report or terminal output. A 401/403 from either
+vendor's API raises `AuthenticationError` naming which environment
+variable to check; the credential value itself never appears in that
+message, a log line, or a traceback. `opencode`, `codex`, and
+`claude-code-personal` need no credential at all -- they read local
+files only, never a network call.
+
+The one other untrusted input this package reads is an imported CSV file
+(`--before-csv`/`--after-csv`): `adapters/csv_import.py` strips C0
+control characters (`\x00`-`\x1f`) from every cell before it can reach
+the terminal summary, closing a terminal/ANSI-escape-injection path a
+crafted `user_email` or `cost_usd` cell could otherwise open. Nothing
+read from an API response or a CSV file is ever passed to `eval`, `exec`,
+or a shell -- both adapters and the CSV importer only parse and validate
+(`require_field` in `http_client.py` raises `SchemaDriftError` rather
+than guessing when a vendor field is missing).
+
+The JSON report file (`teamspend-snapshot-*.json`) contains real per-user
+emails and dollar amounts, so `output.py` writes it with `0600`
+(owner-read/write-only) permissions via `os.open(..., O_CREAT |
+O_WRONLY, 0o600)` -- avoiding the umask-then-chmod race a separate
+`chmod` call after write would leave open -- and the CLI auto-scaffolds a
+`.gitignore` entry for that file pattern on first run.
+
+**What's out of scope**: the accuracy of a vendor's own admin-API
+response (a wrong number from Cursor's or Anthropic's API is a report for
+that vendor, not teamspend), and findings that assume a credential has
+already been put somewhere insecure by the user (a committed `.env` file,
+a world-readable shell history) -- teamspend reads credentials only from
+environment variables it does not set or persist itself.
+
+To report a vulnerability, use
+[GitHub Security Advisories](https://github.com/RudrenduPaul/teamspend/security/advisories/new)
+rather than a public issue -- see
+[SECURITY.md](https://github.com/RudrenduPaul/teamspend/blob/main/SECURITY.md)
+for the full policy and response timeline. **Honest note**: this project
+does not currently publish SLSA provenance, Sigstore signatures, or an
+SBOM, and has no OpenSSF Scorecard badge set up -- none of that
+infrastructure exists yet for either distribution, so it isn't claimed
+here. Both distributions have zero runtime dependencies (this package
+uses only `urllib` from the standard library), so there is no
+third-party HTTP client to audit in the request path.
+
+## Development
+
+```bash
+cd python
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+Source lives under `python/src/teamspend/`, laid out to mirror the
+TypeScript module structure 1:1 (`adapters/`, `compare.py`, `output.py`,
+`cli.py`, `types.py`, `errors.py`, `http_client.py`) so a change in one
+codebase has an obvious counterpart to check in the other. See
+[CONTRIBUTING.md](https://github.com/RudrenduPaul/teamspend/blob/main/CONTRIBUTING.md).
+
+## License
+
+Apache 2.0.