Abuse Prevention

Abuse can happen in many ways, the most common are:

• Abusing storage (both for packages and Git repositories)
• Abusing CPU/Memory in CI/CD

Storage Quotas

For the first one, we have quotas in place per user/org. To prevent the creation of many accounts to avoid this limitation and scale horizontally, we reserve the right to monitor potential abuse and take appropriate action. For example, if we see a user/org hitting the limit and just opening other accounts to store similar content, this will fall into the “abuse” category. We’ll moderate such happenings and email the responsible people first. Should we take further actions (e.g. deleting/suspending accounts), we will transparently do so in the CodeFloe Forum and outline the reasoning behind it.

Our Approach to Moderation

We are fully aware that such actions can lead to potential distrust in the platform and a feeling of being treated unfairly or similar. Which is why we want to be fully clear and transparent about it. Most users (99.x%) will never even come close to being affected by such actions. As long as you use the platform in a “normal” way, there is no risk of being limited or suspended.

On the other hand, we (the platform owners) must have the right and options to take actions when it’s appropriate, to also protect other users on the platform and the platform itself.

Last, a reminder: if it is about resources (storage, CPU/Memory) per se, you can always reach out to us to lift your quota limit in exchange for a monthly donation.

Download Traffic

Bytes served for packages, container images and Git LFS objects are attributed to the owning account at the edge proxy and booked into Forgejo once an hour. Forgejo is the single source of truth: the proxy only denies downloads for owners that Forgejo reports as over their limit, so the number on the storage overview and the reason for a block can never disagree. Uploads and Git operations are never blocked by this. See Quotas for the current limits.