Attempts to post the latest Trivy security incident have been marked [dead]

https://news.ycombinator.com/from?site=github.com%2Faquasecurity

Submissions from github.com/aquasecurity | Hacker News

Looks like the repository URL was marked [dead] for several years, I can't tell why. Best to email the moderator (link in footer).

Big security stories often get republished, one might say reviewed and filtered. For this story I see

opensourcemalware.com - https://news.ycombinator.com/item?id=47449498

stepsecurity.io - https://news.ycombinator.com/item?id=47451081

arstechnica.com - https://news.ycombinator.com/item?id=47464996

and 4 others.

Aquasecurity/Trivy GitHub Repository and Homebrew Cask Compromised (again) | Hacker News

Looking at https://news.ycombinator.com/from?site=github.com/aquasecuri... around 2024 when the dead started, a spambot ring was repeatedly posting it?

( Make need to turn on "showdead"; to see it in the 2024 they have similar posts .. )

Submissions from github.com/aquasecurity | Hacker News

Maybe it was intentionally compromised all along.
Oh that's clever. Use the spambot ring to promote the story so that the story gets marked dead because of that! Instead of hiding the news, use the botnet to promote it and use the system against itself.
I've noticed some HN posts get a higher-than-average number of replies from LLM bots. I've wondered if this has a downranking effect due to the upvote/comment ratio, and whether people might be using bots to do this intentionally. Alternatively it could just be that the bots "like" certain keywords more than others.
Please email links to the bot comments to the mods so they can remove this manipulation and its effects.
What's wrong with the report button?
Yea, this looks like a lingering auto-moderation on the Github repo URL prefix due to past spam attempts.