petergpt/bullshit-benchmark: README-based editorial guide

petergpt/bullshit-benchmark describes itself in the README as "BullshitBench measures whether AI models challenge nonsensical prompts instead of confidently answering them, created by Peter Gostev.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: BullshitBench measures whether models detect nonsense, call it out clearly, and avoid confidently continuing with invalid assumptions.. That establishes the project's stated boundary, not a production test.

The README's "Latest Changelog Entry (2026-07-31)" section gives a useful starting point for deciding whether the project fits: In v1, xhigh scored 0.9212 versus 0.5939 for none; in v2, xhigh scored 1.0700 versus 0.6600 for none.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Added the July 31 re-post-trained deepseek/deepseek-v4-flash-0731 revision to both published benchmark tracks at none and xhigh reasoning.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "1. Detection Rate by Model (Main Chart)". The source evidence includes: Primary leaderboard-style view showing each model's green/amber/red split. The screenshot uses the viewer's 30-day new-model filter so recent additions remain legible.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: README 没有给出可直接复制的安装命令。 When the README contains no runnable command, this article does not invent one. Open its "v2 Changelog Highlights" section and confirm system dependencies, default ports, and first-run initialization before using a public server.