Skip to content

Commit 5860730

Browse files
authored
docs(readme): remove star history chart (#30)
1 parent 214af18 commit 5860730

3 files changed

Lines changed: 0 additions & 7 deletions

File tree

.lycheeignore

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@
1010
# Badge / image hosts that rate-limit CI crawlers; a stale badge is cosmetic, not a 404.
1111
img\.shields\.io
1212
hub\.docker\.com
13-
star-history\.com
1413

1514
# npm's registry returns 403 Forbidden to non-browser crawlers (bot protection), so the
1615
# package page is not fetchable from CI. PyPI, by contrast, is checked normally.

README.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -586,12 +586,6 @@ BSD-3-Clause for the Fortress patches and tooling (matching Chromium). Chromium
586586

587587
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.
588588

589-
<a href="https://www.star-history.com/?repos=tiliondev%2Ffortress&type=date&legend=top-left">
590-
<img alt="Star History Chart" src="docs/assets/star-history.png" width="720" />
591-
</a>
592-
593-
<br/>
594-
595589
<em>Stealth you can read, rebuild, and run yourself.</em>
596590

597591
</div>

docs/assets/star-history.png

-352 KB
Binary file not shown.

0 commit comments

Comments
 (0)