Appology！Request to lift permanent cooldown — first-time resource submission (cc-statistics)

[androidZzT]

Hi @hesreallyhim,

I submitted cc-statistics as a resource recommendation (Issue #1490) and it was closed due to a
permanent cooldown on my account.

I believe this may be an error — this was my first submission to this repository. I don't recall
submitting any prior issues here. It's possible that some automated activity on my GitHub
account (CI/CD, API usage from development tools) may have triggered the cooldown detection.

About the resource:
cc-statistics is the only open-source usage monitor that supports 4 AI coding platforms (Claude
Code + Gemini CLI + Codex CLI + Cursor) in one tool. It ships a native macOS SwiftUI menu-bar
app, CLI, and web dashboard. MIT licensed, 100% local, zero dependencies.

Repo: https://github.com/androidZzT/cc-statistics

I'd really appreciate it if you could review and consider lifting the restriction so I can
resubmit. Happy to provide any additional information.

Thank you for maintaining such an amazing resource for the Claude Code community!

[hesreallyhim]

hi @androidZzT thank you for sharing your resource, it looks very cool. If what you're saying is true, then you should definitely inspect your system and review all of your workflows, and probably rotate your credentials. I already found the previous submissions that were made on your behalf, each with escalating cooldown duration. You should be aware that when you authorize an app or give your credentials to a bot or any other automation, you are authorizing that bot to act on your behalf - so that's why it's important to be really vigilant about your credentials and to rotate them regularly.

1st) #1015
2nd) #1016
3rd) #1489
4th) #1490

I can't change the policy in your case, however, because of my extremely good nature, I will probably eliminate the lifetime ban and max it out to 90 days or something, which should be enough to fend off any spammers. So, you should check back in, and if I adopt this change and you are still building with Claude Code in 90 days, you can feel free to submit again. Fortunately, in any case the restriction is not against your app, it's a restriction on your interactions - which is to say, if you make something awesome, I will find it, and I will share it.

In this case, for what it's worth, it seems to me that one of your strongest unique selling points is that the app supports many providers. From a product point of view, that's probably a strong choice - but for a list of special claude code resources, it has the opposite effect, because I tend to prefer resources that are specific to Claude Code.

I encourage you to keep up the good work, and rest assured that your app is still eligible for inclusion on the list, and I encourage you to monitor what your tokens are doing - because, as I mentioned, when you give access with your credentials, you are letting things act on your behalf. You can review your Security Log in your profile Settings if you want to see what activity has been going on.