Repository navigation
Allow blacklisting GitHub users, organizations, or DNS namespaces #98
Description
This is a fallback in case we do we have spammers or other bad actors succeed in publishing malicious/spam content.
This should be possible in some code in this repo where we have git logs to audit history of changes.
Adding someone to this list should optionally delete everything they've published historically.
Activity
domdomegg commentedon Aug 27, 2025
Another idea: we could require GitHub users have had their account for a while, e.g. 30 days. This would add more friction to malicious users creating new accounts when they are banned. I won't do this for go-live but we can explore it if it becomes a problem.
(Although it might add a little more friction to genuine users with fresh GitHub accounts, I know a couple people who created GitHub accounts to build and share MCP servers so it would be sad to block them - so think we can see how we go and then do this if the spam becomes apparent)
feat: add namespace blocking functionality for JWT authentication
feat: add namespace blocking functionality for JWT authentication (#313)