If you respect your time and effort, only pick programs that are "Triaged by HackerOne".
This is the second time I've hit the same pattern, and both times it came from a program that triages its own reports.
First program, not H1-triaged, report closed as Duplicate with no proof offered, and when I pushed back, the reply was, word for word:
"Oh, sorry, that's an internal finding we've got for this, not a HackerOne report. Now, I appreciate you've got no way to corroborate this, but please take my word for it; we wouldn't do that to withhold a bounty."
Second program, also not H1-triaged, and this one is worse.
I reported an authentication flaw: an attacker could take standing control of an account bound to someone else's email address, and permanently lock the real owner out of it. The owner could prove they owned that email address and still could not get into the account.
The program asked me for more evidence, so I re-ran the entire flow by hand, recorded it end to end, and sent it the same day, after which they triaged it, rated it Critical, and set it to Pending Bounty.
Then it sat there for 110 days.
When a reply finally came, it was from a newly hired staff member, the severity went from Critical to None, and the report was closed as Informative. The stated reason was that the previous program manager had "mislabeled the severity because of AI agents", and it was also, apparently, "a known bug which we've discovered in internal pentests" and "a risk we've decided to accept".
Here is the part that bothers me most. The reason given for closing it was, quote:
"A user logging in to an attacker prefilled account has very little security impact."
That is not what I reported, and nobody reported that, because the victim in my report is the person who owns the email address, who ends up locked out of an account they never created and cannot get into even after proving to the application that the address is theirs. The closure does not mention that anywhere, and it was the entire subject of the extra evidence the program itself asked me for.
You can disagree with a severity, but you cannot disagree with a finding you have not read.
The through-line in both cases is an unverifiable claim that they already knew, from a program with nobody independent in the loop.
I have no problem with a program declining a report, and accepted risk is a legitimate business decision, but it is a decision about whether to fix something, not a statement that the impact does not exist, and "we knew already, take our word for it" is not something I can check, dispute, or learn anything from.
When a program self-triages, there is no neutral party between you and that call, so price that in before you spend a month on their scope.