COPPICE

Terms of Service

Last updated 23 August 2026

These terms cover coppice.tekreign.com, GitHub authorization, and the Coppice extension in Cursor / VS Code. The operator is TekReign.

Intended use

Coppice is architecture hygiene for vibe-coded repos: one structure, one library per job, no duplicate features, orphan cleanup, and CVE checks at the exact lockfile version. You keep prompting in Cursor. Coppice writes COPPICE.md and a Cursor rule so the next agent extends what exists.

The website is GitHub-linked project history. It is not a second IDE, not a Replit-like workspace, and not a GitHub App as the product.

Limitations

Local Scan Workspace covers JS/TS and a first pass for Python. No Cursor API key.
Agent Scan (Python and other languages) is on-demand, billed to your Cursor plan, and is not run automatically on lockfile scan.
The engine does not invent CVEs. It matches OSV at the resolved version.
Dashboard history only appears if the API is deployed and you upload after signing in. A Vercel-only landing deploy has no GitHub login.
Coppice does not clone your GitHub repo in the cloud as the product.

Your content

You remain responsible for code in your repositories. Scan artifacts you upload (contracts and findings) are treated as your project data, not as public social posts. We do not run a user-generated media feed. There is no in-app commenting community to moderate.

Do not upload secrets. Do not use Coppice to attack systems you do not own. If we find abuse of the API (credential stuffing, scanning other people’s private tokens, malware distribution), we may revoke GitHub access and delete the account.

GitHub

GitHub’s terms also apply to OAuth. You can revoke Coppice at any time in GitHub application settings. Scopes are described in the Privacy Policy.

No warranty