cceco
Claude Code environmental impact tracker. Reads local session history and shows energy, GHG, water, metals, and fossil fuel usage via EcoLogits.
Also made with Claude code and superpowers.
Install
pipx install cceco
Usage
cceco # all time
cceco --since 2026-06-01 # from a date
cceco --since 2026-06-01 --until 2026-06-09 # date range
cceco --tokens # also show token breakdown
Example output
Claude Code Environmental Impact
Period: all time (3 projects, 12 sessions, 47 requests)
── claude-sonnet-4-6 ──────────────────────────────────
Electricity 0.042 kWh [0.031 – 0.053]
GHG 0.018 kgCO2eq [0.013 – 0.023]
Water 0.12 L [0.09 – 0.15]
Abiotic depl. 4.2e-09 kgSbeq [3.1e-09 – 5.3e-09]
Fossil fuels 0.61 MJ [0.45 – 0.77]
With --tokens:
── claude-sonnet-4-6 ──────────────────────────────────
Tokens input: 1,234,567 output: 89,012
cache creation: 345,678 cache read: 234,567
Electricity ...
Development
git clone https://github.com/icij/cceco
cd cceco
uv sync
uv run cceco
uv run pytest
Notes
Impact is calculated using EcoLogits from the total tokens that require GPU
computation per model: input_tokens + cache_creation_input_tokens + output_tokens. Cache-read tokens are excluded because they are cheap
key-value cache lookups rather than full forward passes.
This matches what you would enter manually in the EcoLogits web calculator.
Metadata
Release files for icij-cceco 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| icij_cceco-0.1.0.tar.gz | 31.3 kB | Without provenance | Details for icij_cceco-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| icij_cceco-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for icij_cceco-0.1.0-py3-none-any.whl |
Total release size: 37.9 kB
Release files / icij_cceco-0.1.0.tar.gz
| Download URL | icij_cceco-0.1.0.tar.gz |
|---|---|
| Size | 31.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae980aa1c3f73009a42673f2822913c03eb2de8071f51a29ffba8acdba1ff4c6
|
|
BLAKE2b-256 checksum How to use checksums |
8a9b3926e4599928c61d17a5603cf3c9db898cd0e6ef86a487e8d170e1994415
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / icij_cceco-0.1.0-py3-none-any.whl
| Download URL | icij_cceco-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36d17be00300196c7af0604135477187511da4bfafe1e5af6bbfd4601d13a0bf
|
|
BLAKE2b-256 checksum How to use checksums |
5fd8d5c9afda0be1719b1ffb355175e2a16b02f88f68d19da2fb46913d5258b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for icij-cceco 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.