diff --git a/.lycheeignore b/.lycheeignore
index 3b964ed..e4fb626 100644
--- a/.lycheeignore
+++ b/.lycheeignore
@@ -10,7 +10,6 @@
 # Badge / image hosts that rate-limit CI crawlers; a stale badge is cosmetic, not a 404.
 img\.shields\.io
 hub\.docker\.com
-star-history\.com
 
 # npm's registry returns 403 Forbidden to non-browser crawlers (bot protection), so the
 # package page is not fetchable from CI. PyPI, by contrast, is checked normally.
diff --git a/README.md b/README.md
index 925a3fc..9293196 100644
--- a/README.md
+++ b/README.md
@@ -586,12 +586,6 @@ BSD-3-Clause for the Fortress patches and tooling (matching Chromium). Chromium
 
 Detection keeps moving, so a stealth engine is only as good as its last rebase. Fortress tracks the latest Chromium monthly, re-runs the full gauntlet, and ships a patch whenever a detector finds a new tell, so what you run keeps matching what a real Chrome install looks like. [Watch the releases](https://github.com/tiliondev/fortress/releases) to follow the `v2` MaskConfig work, or [star the repo](https://github.com/tiliondev/fortress/stargazers) if it's useful to you.
 
-<a href="https://www.star-history.com/?repos=tiliondev%2Ffortress&type=date&legend=top-left">
- <img alt="Star History Chart" src="docs/assets/star-history.png" width="720" />
-</a>
-
-<br/>
-
 <em>Stealth you can read, rebuild, and run yourself.</em>
 
 </div>
diff --git a/docs/assets/star-history.png b/docs/assets/star-history.png
deleted file mode 100644
index c8bf032..0000000
Binary files a/docs/assets/star-history.png and /dev/null differ