The source of tuff-app.github.io: the TUFF homepage and the benchmark leaderboard.
| Path | What it is |
|---|---|
index.html |
The homepage |
benchmarks/ |
The leaderboard page and its script |
assets/ |
TUFF 11 app screenshots, icon and chip animation |
TUFF/ |
Redirects from the old tuff-app.github.io/TUFF/ addresses |
It's plain HTML, CSS and JavaScript with no build step. To preview it, run
python3 -m http.server here and open http://localhost:8000.
The homepage uses the supplied TUFF 11 screenshots, a user-controlled expert-streaming diagram and concise installation requirements. Shared styles live in assets/site.css. The benchmark data and filters retain their existing behavior.
The leaderboard data isn't stored here. Every hour, and on each push,
.github/workflows/deploy.yml reads the reviewed posts in TUFF's
Benchmarks discussions
with TUFF's Scripts/benchmark_discussions.py, writes benchmarks/data.json
and deploys the site. Nothing in a post is ever executed. See
how benchmarks work.
TUFF is one project split across a few repositories:
| Repository | What's in it |
|---|---|
| TUFF | The Mac app, the tuff command and the inference engines |
| sandbox | The Linux VM that runs web and file search in isolation |
| homebrew-tap | The Homebrew cask |
| tuff-app.github.io | The website and benchmark leaderboard |
They all follow the same contributing guide, maintainer roles and code of conduct. Questions and ideas go in Discussions.
Please don't open a public issue for a security problem. Report it privately through GitHub's vulnerability reporting on the repository it affects, or on TUFF if you're not sure which. The security policy has the details.
Apache 2.0. Model weights keep their own terms.