Skip to content

Commit 8ce496c

Browse files
docs: deprecate crono-export-cli (Cronometer ToS 10(b) + GPL-2.0 contamination)
Cronometer's Terms of Service Section 10(b) prohibits AI/LLM use of their content, which is the primary use case this tool was built for. Additionally, the GPL-2.0 license of the underlying gocronometer dependency is incompatible with this repo's MIT license, creating a license-compliance defect in all shipped binaries. This change adds a deprecation notice at the top of the README. No code changes; no new release. The deprecation decision is tracked in quantcli/common QUA-12. Co-Authored-By: Paperclip <noreply@paperclip.ing>
1 parent af97fdf commit 8ce496c

1 file changed

Lines changed: 19 additions & 0 deletions

File tree

README.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,24 @@
11
# crono-export-cli
22

3+
> ## ⚠️ Deprecated — do not use for new deployments
4+
>
5+
> This tool is **deprecated** and will not receive further development, releases, or security patches.
6+
>
7+
> **Why:**
8+
>
9+
> 1. **Cronometer's Terms of Service prohibit the AI/LLM use case this tool was built for.** [Section 10(b) of Cronometer's Terms](https://cronometer.com/terms/) forbids using Cronometer content to train, ground, or otherwise feed AI/LLM systems — exactly the workflow `crono-export-cli` was designed to enable. We cannot in good conscience continue distributing a tool whose primary intended use violates the upstream service's terms.
10+
> 2. **The underlying dependency carries a GPL-2.0 license that is incompatible with this repo's MIT license.** `crono-export-cli` depends on [`jrmycanady/gocronometer`](https://github.com/jrmycanady/gocronometer), which is GPL-2.0. Statically linking GPL-2.0 code into an MIT-distributed binary creates a license-compliance defect in every binary we have shipped. The pre-built binaries on the releases page are affected.
11+
>
12+
> **What you should do:**
13+
>
14+
> - **For your own data:** Cronometer's web UI offers a manual data export (Settings → Account → Export Data) that covers servings, nutrition, biometrics, exercises, and notes. Use that instead.
15+
> - **Existing binaries:** prior releases remain available on the [releases page](https://github.com/quantcli/crono-export-cli/releases) for archival reference, but should not be used for new deployments — they carry the license defect described above, and any use against the live Cronometer service still implicates the ToS issue.
16+
> - **Tracking issue:** see [`quantcli/common` QUA-12](https://github.com/quantcli/common) for the deprecation decision and rationale.
17+
>
18+
> The rest of this README is preserved as historical documentation.
19+
>
20+
> ---
21+
322
Export your personal nutrition, biometric, and food-log data from [Cronometer](https://cronometer.com) as narrow markdown (the default) or JSON. Built for personal LLM agents and scripts that want structured nutrition data — for example, an LLM-driven bariatric or fitness coach that needs to know how much protein, B12, iron, or calcium you actually got today.
423

524
[![Latest Release](https://img.shields.io/github/v/release/quantcli/crono-export-cli)](https://github.com/quantcli/crono-export-cli/releases/latest)

0 commit comments

Comments
 (0)