That said, I guess it's got some value in that it forces someone to become a squeaky wheel by bumping an issue they want to get fixed?
> 10. User Protection
> You must not engage in activity that significantly harms other users. We will resolve disputes in favor of protecting users as a whole.
I can see a lot of arguments that GitHub could use to label any kind of automatic "bumpbot" bot/tool/service in widespread use as violating this clause. If I was more confident it wouldn't get ban-hammered and shutdown, I'd pop back open that folder of notes and get at it.
Making a completely automated bot certainly falls short of GitHub's acceptable use policy.
On second thought... maybe not. I could see it quickly becoming a battering ram that just annoys OSS devs. Ultimately, this isn't something users can't improve, it has to be the maintainer. Nagging OSS maintainers is how we wind up with incidents like left-pad. In the most extreme of circumstances, if a maintainer is hiding issues behind the stale bot, it could be interpreted as abandonment and a fork should be made.
Sometimes a bump is a "Hey, just incase you forgot" so automatically closing is just "Ok I forgot this, but who cares now" attitude.