Codeberg
Non-profit, community-owned code hosting platform built on Forgejo, offering Git repositories, CI/CD, Pages hosting, and collaborative development tools as a privacy-respecting alternative to GitHub.
Score generated by AI agents based on publicly cited evidence and reviewed by the project maintainer. Not independently validated. Last assessed 2026-10-30.
Score History
Timeline events are AI-curated from public reporting. Score trajectory is derived from documented events.
Codeberg.org launched in January 2019 as a donation-funded, EU-hosted Gitea instance run entirely by volunteers on rented cloud machines. It grew from 379 users in its first month to over 10,000 by April 2021, added Pages custom domains and a Woodpecker CI alpha in 2021, and hired its first paid mini-job employee in May 2022. Resource limits appeared early, with automatic mirror creation disabled in March 2020.
After Gitea's domains and trademark moved to a for-profit company, Codeberg launched Forgejo on December 15, 2022 as a community fork, having just moved its core service onto its own hardware in Berlin. An NLnet grant funded federation work, Forgejo Actions arrived experimentally, and membership grew to about 400. Paid labor remained a single part-time role, and a January 2024 DDoS disrupted service.
Forgejo became a hard fork of Gitea in February 2024, moved to GPLv3+ with v9.0 and gained a quota system. Codeberg began paying effort compensations to four contributors and a freelancer, rehired a founding member part-time, and expanded its Ceph storage cluster. It announced storage quotas in October 2024 but did not yet enforce them, and it handled a far-right spam campaign in February 2025.
Codeberg began enforcing heuristic storage limits on May 16, 2025, the same month GNU Guix moved to the platform; Zig and Gentoo followed, and users passed 200,000 by November 2025. Growth brought strain: AI crawlers slowed the site in August 2025, database slowdowns recurred, and the old Pages server is being retired. Governance became more international and transparent, with public budgets from May 2026, while July 2026 member votes barred mostly LLM-generated and cryptocurrency projects.
Alternatives
Full DevOps platform with built-in CI/CD, container registry, and project management. Moderate switch — similar Git workflow but different CI configuration. Open-core model means some features are enterprise-only. Can be self-hosted.
Microsoft-owned code hosting platform with CI/CD through Actions and extensive integrations. Easy switch — Git repos are portable, while issue and CI workflows may need migration.
Minimalist, email-driven code hosting platform. Hosting plans currently start at $4/month, with financial aid available and no payment required just to contribute to existing projects. Hard switch for most — email-based workflow differs significantly from a web-based PR model.
In the News
Dimensional Breakdown
Summaries below were written by AI agents based on the cited evidence. They are editorial interpretations, not independent research findings.
Dimension History
Timeline (60 events)
Codeberg.org launches as non-profit code hosting platform
Codeberg e.V., founded in September 2018 by 7 members, launches Codeberg.org (formerly teahub.io) as a non-profit collaboration community for free and open-source projects. The platform runs on Gitea and is hosted in the EU to avoid DMCA abuse risks. About 480 EUR in donations covered initial legal and infrastructure costs.
First month: 25 members, 333 repositories, 379 users
After one month of operation, Codeberg e.V. has 25 active members and the platform hosts 333 repositories created by 379 users. Backups are managed on private offline machines by founding members at no cost, while the live service uses rented cloud virtual machines.
Codeberg crosses 1,000 repositories and 3,500 users
By October 2019, Codeberg hosts 1,582 repositories maintained by 3,530 users, with organic growth of 33% month-over-month in repositories and 69% in users. The rapid growth demonstrates demand for a non-profit, EU-hosted code forge alternative.
Codeberg disables creation of new automatic mirror repositories
Codeberg disabled creation of new mirror repositories after finding that many mirrors were abandoned, skewed toward very large projects, and kept consuming resources; some users had created over 100 mirrors of large open-source repositories. Existing mirrors continued to update, and users could still mirror manually with Git.
Codeberg reaches 70 e.V. members in June 2020
By June 2020, Codeberg has 70 association members, including 53 with active voting rights and 17 supporting members. It hosts 4,054 repositories with 3,171 users, up 17.5% and 12.5% from the previous month.
Codeberg publishes its legal position after the RIAA's youtube-dl takedown
Two days after the RIAA's October 23, 2020 DMCA notice shut down youtube-dl development on GitHub, Codeberg published its analysis of how it would handle such a request. It said a DMCA request by itself was not an issue for an EU-based host, but that the RIAA's reliance on German copyright law meant Codeberg could face similar requests.
Codeberg doubles in size to 8,357 repos and 6,952 users
By December 2020, Codeberg hosts 8,357 repositories and 6,952 users, roughly doubling the mid-year figures. Monthly growth rates of 12-13% persist. The platform still runs on rented cloud infrastructure with no paid staff.
Codeberg reaches 10,000 users milestone
Codeberg crosses 10,000 registered users and 11,877 repositories in April 2021. Its 10,567 users are about 28 times the 379 reported after its first month in early 2019. The milestone signals that Codeberg has moved beyond its initial user base into a functional alternative for open-source projects.
Codeberg asks maintainers to remove personal data from the cloudflare-tor repository
After receiving multiple requests, Codeberg asked the maintainers of the crimeflare/cloudflare-tor repository to remove lists of usernames it considered private data used for public shaming, citing its Terms of Service and German law. It said GDPR requests oblige it to remove such data, its history and all copies, including forks.
Codeberg e.V. reaches 100 active association members
Codeberg e.V. passes 100 active association members with voting rights, a key governance milestone. The growing membership base strengthens the democratic foundation of the organization and its ability to make representative decisions at the annual assembly.
Codeberg launches Woodpecker CI closed alpha
Codeberg launches a closed alpha test of its CI service using Woodpecker, a libre fork of Drone CI. The CI runs on Codeberg's bare-metal server. Access is granted on request while the team tunes quotas and abuse prevention. Approximately 60 projects sign up in the first weeks.
Codeberg Pages adds custom domain support
Codeberg launches the next version of its Pages server for static website hosting on December 2, adding custom domains and serving from different pages and repositories.
Codeberg hires first employee as German mini-job at 450 EUR/month
Codeberg e.V. becomes an employer for the first time, hiring an honorary member part-time as a tax-exempt German mini-job at 450 EUR/month for approximately 10 hours/week. The employee, a veteran Gitea maintainer, works on Woodpecker CI, Codeberg Pages, and infrastructure. Total cost including insurance is approximately 600 EUR/month.
Software Freedom Conservancy launches Give Up GitHub campaign recommending Codeberg
The Software Freedom Conservancy launches its 'Give Up GitHub' campaign in response to GitHub Copilot's use of open-source code for AI training. The campaign notes Codeberg, based on Gitea, as an available alternative for hosted services.
Codeberg experiences 65-minute outage after routine server update
Following a routine server update and reboot at netcup, Codeberg's main Gitea service goes down for approximately 65 minutes due to a Ceph network filesystem configuration issue that failed to remount properly. Two additional shorter outages follow on August 29 and September 6 from suspected DDoS or crawler flooding.
Gitea domains and trademark transferred to for-profit company without community consent
Gitea founder Lunny Xiao transfers the gitea.io and gitea.com domains and 'Gitea' trademark to Gitea Ltd, a newly formed for-profit company, without community knowledge or approval. The community publishes an open letter on October 28 demanding restitution. Gitea Ltd refuses, confirming they now control the project entirely.
Codeberg schedules core hosting migration to its own server in Berlin
Codeberg announces plans to move its core Gitea service from a rented cloud instance to its own physical server in Berlin. It schedules work for November 14–16, with planned downtime for the final migration on November 16. Woodpecker CI, Pages and Weblate were already running on its own hardware, and project data was being moved to Ceph storage.
Forgejo begins €50,000 NLnet grant for federation work
A €50,000 NLnet grant to further forge federation begins on December 1, 2022. The contemporaneous project updates point readers to the Forgejo feature branches for progress.
Codeberg launches Forgejo as community fork of Gitea
After Gitea Ltd's takeover of the Gitea project, Codeberg e.V. announces Forgejo on December 15, 2022 as a community-driven fork. Codeberg says it will use Forgejo instead of Gitea starting with version 1.18.0, describing it as a drop-in replacement and a new home for the Gitea community.
Forgejo announces integrated CI/CD feature called Actions
Forgejo announces an experimental integrated CI feature in v1.19, with syntax similar to GitHub Actions but no guarantee of compatibility. Unlike the existing Woodpecker CI integration, which uses a separate interface and webhook-based notifications, Forgejo Actions displays results directly in the forge UI. Users can connect runners to execute workflows; the feature is not yet ready for production.
Codeberg holds its annual assembly and forms a new presidium
Codeberg reports that an extremely long but productive annual assembly took place at the end of May 2023. A new presidium was formed and decided to publish its decisions to members internally; five new honorary members were welcomed.
Forgejo agrees to accept copyleft contributions
In June 2023, Forgejo agrees to accept copyleft contributions after months of discussion. This agreement leads to the GPLv3+ change for versions starting with v9.0 in 2024. Forgejo says copyleft enables reuse of compatible dependencies and reduces the risk of modified proprietary versions trapping users.
Codeberg launches updated membership registration system
Codeberg’s long-awaited updated membership registration form goes live in October 2023. The organization reports 401 members, including 281 with active voting rights, 113 supporting members and 7 honorary members. Codeberg says it hopes the form is more visually appealing and clearer about membership and payment options. A later follow-up on January 30, 2025 reports that overhauled member-management tooling reduced accepting or refusing an application from several minutes to a single click, enabling quicker responses and less time spent on bureaucracy.
Forgejo v1.21.1-0 release notes describe user blocking introduced in v1.20
Forgejo releases v1.21.1-0 and describes its user-blocking feature, introduced in v1.20 and deployed on Codeberg. Blocking cancels repository transfers originating from the blocked user and removes that user as a collaborator on repositories owned by the user doing the blocking.
Codeberg hit by DDoS attack alongside Sourcehut
Codeberg loses reliable network connectivity on January 11, 2024 during a DDoS attack that fills its and its provider’s uplink capacity. The provider restricts IPv4 traffic and restores IPv6 access, and Codeberg uses spare cloud capacity as a proxy to restore access. Codeberg suspects a connection to SourceHut’s concurrent DDoS or its status page being hosted on Codeberg Pages, explicitly calling that connection speculation.
Codeberg begins paying voluntary effort compensations to four contributors
Codeberg e.V. starts paying voluntary effort compensations to four contributors and hires a freelancer for Forgejo work, marking a significant expansion of funded development beyond the single mini-job employee. The organization has grown to 429 members. This addresses chronic underfunding of maintainer labor.
Forgejo becomes hard fork of Gitea
Forgejo announces its decision to become a hard fork of Gitea, developing independently as governance and development models diverge. The decision enables architectural and workflow changes without having to preserve compatibility with the upstream codebase. Users can still upgrade from the latest Gitea version released at the time of the fork, but compatibility with later Gitea versions is no longer guaranteed.
Forgejo v7.0 releases as first Long Term Support version
Forgejo v7.0 ships as the project's first Long Term Support (LTS) release, adopting Semantic Versioning 2.0.0. New features include SourceHut Builds integration, source code search via git grep by default, and translations in four new languages. LTS support runs until July 2025, signaling Forgejo's maturity as production software.
Forgejo v8.0 ships foundations for federation and data portability
Forgejo v8.0 releases with building blocks for ActivityPub federation and data portability, including an internal test in which starring a repository also stars its federated counterpart. These foundations are not yet used for user-visible features. Self-registration is disabled by default on the installation page to prevent spam abuse. A newly created UI team aims to reduce random interface changes.
Forgejo announces license change to GPLv3+ starting with v9.0
Forgejo formally announces that versions starting with v9.0 will be licensed under GPLv3+ instead of MIT. The project says copyleft reduces the risk of exploitative proprietary modifications and vendor lock-in. Older versions remain MIT-licensed. The governance decision to accept copyleft contributions was made in June 2023; copyleft makes reuse of compatible dependencies easier, while incompatible dependencies had to be removed.
Codeberg e.V. grows to 556 members, rehires founding member part-time
Codeberg e.V. reaches 556 members (386 with active voting rights). The organization rehires a founding member part-time for Codeberg work and announces a focus on usability and user research. Forgejo's direct donation mechanism is also established, allowing contributors to receive funding outside Codeberg e.V.'s budget.
Codeberg reconsiders OSI license requirement amid AI definition controversy
A community discussion opens on whether Codeberg should update its Terms of Use if the OSI publishes its Open Source AI Definition (OSAID) without requiring training datasets to be open. The OSAID appears to differ from the original Open Source Definition by allowing proprietary datasets. The debate highlights tensions between Codeberg's principled FOSS-only stance and evolving definitions.
Forgejo v9.0 ships under GPLv3+ with configurable quota system
Forgejo v9.0 releases as the first version under the copyleft GPLv3+ license. It introduces a flexible, configurable storage quota system — a feature that required architectural changes incompatible with the Gitea codebase and would not have been possible before the hard fork. Push mirrors gain SSH key authentication support.
Codeberg announces storage quota to combat resource abuse
Codeberg announces introduction of default storage quotas using Forgejo v9’s new quota feature to combat resource abuse. The total of non-promoted personal and private repository content should not exceed 100 MiB. Free/libre projects needing more resources can request exceptions without storage charges. The policy implements a May 2023 assembly decision.
Fedora selects Forgejo as its replacement Git forge
The Fedora Council chooses Forgejo to replace Fedora’s Git forges, including package sources at src.fedoraproject.org and general hosting at pagure.io. Migration is to proceed in phases, beginning with dist-git. At this announcement, Bugzilla’s future remains under discussion. Codeberg is cited as a reference deployment supporting more than 143,000 registered users.
User reports hotspot-specific access problem after late-November Codeberg shutdown
A Codeberg Community issue reports that one user could not access Codeberg repositories and hosted domains from a particular Wi-Fi hotspot after a high-traffic shutdown at the end of November 2024. Another hotspot on the same home network could access Codeberg normally.
Forgejo v10.0 releases with improved issue search
Forgejo v10.0 ships with improvements to issue search using bleve, applying fuzzy search per word. The release continues the rapid quarterly cadence established after the hard fork, with each version incorporating features unique to Forgejo that diverge further from the Gitea codebase.
Codeberg expands Ceph cluster to three nodes and prepares service clustering
Codeberg expands its Ceph storage cluster to three nodes, upgrades it to Reef, and uses 8TB Kingston DC600M SSDs alongside HDD-backed storage. The storage cluster can continue working through a server reboot or failure. Galera database replication has been successfully tested, with a production-data dry run planned; virtual floating IPs are planned to distribute services and prepare for failover.
DDoS attack targets Forgejo's code.forgejo.org instance
Starting February 9, 2025, code.forgejo.org is disrupted by DDoS-like traffic from thousands of IP addresses. Waves involved 10,000–50,000 IPs. After two days of slowness and occasional disruptions, blocking the 500 most active IP ranges stopped over 90% of the traffic and restored service. The traffic continued until February 18; Forgejo said it was unclear whether this was malicious or excessive crawling. The retrospective describes an early disruption that recovered after a few minutes.
Codeberg responds to far-right hate campaigns with moderation tools
Codeberg publishes a statement addressing hate campaigns by far-right forces targeting projects advocating tolerance and equal rights. Attackers exploited the notification system to mass-spam abusive messages to 100 users at a time, overwhelming the mail server. Codeberg deletes attacker accounts, blocks the abused functionality, and pursues NLnet-funded moderation tooling for Forgejo.
Forgejo v11.0 ships as second Long Term Support release
Forgejo v11.0 releases as the second LTS version, supported until July 2026. The quarterly release cadence and LTS commitments demonstrate Forgejo's maturation as production-grade software, giving organizations like Codeberg confidence in long-term stability for their deployments.
GNU Guix announces migration from Savannah to Codeberg
The GNU Guix project accepts its plan to migrate Git repositories, bug tracking and patch tracking to Codeberg to improve contribution experience, reduce labor-intensive infrastructure work and strengthen quality assurance. The accepted plan schedules repository migration by June 7, keeps the Savannah repository as a mirror for at least one year, and accepts bug reports and patches via both email and Codeberg through December 31, 2025.
Codeberg begins enforcing default storage limits with heuristic quotas
Codeberg began gradually applying storage restrictions on May 16, 2025: 750 MiB of Git storage plus 1.5 GiB for LFS, packages, releases and attachments, and no more than 100 MiB of personal or private content. Heuristics based on factors such as account age, contributions, membership and project popularity manage quotas for most users; new users planning large migrations will probably have to contact Codeberg first. Codeberg does not charge for extra resources.
GNU Guix completes migration to Codeberg
GNU Guix’s canonical repository migration to Codeberg takes effect on May 25, 2025. The canonical URL becomes https://git.guix.gnu.org/guix.git, redirecting to Codeberg, while the old Savannah URL remains valid for at least one year. Other project repositories had already migrated when the May 22 announcement was published.
AI crawlers bypass Codeberg's Anubis defense and slow the site
Codeberg staff said AI crawlers had learned to solve the challenges of Anubis, the proof-of-work tool it used to keep bots out, causing a period of extreme slowness. Codeberg said some of the bots appeared to run on Huawei-controlled networks and moved to blocking offending IP ranges directly.
Codeberg hires second part-time employee for administrative support
Anja Hänel joins Codeberg's virtual office team as a second part-time employee, handling administrative matters and relieving system administrator Andreas Shimokawa from office tasks. This represents continued institutional growth, though the organization's paid staffing remains minimal relative to its 200,000+ user base.
Codeberg's reworked Privacy Policy takes effect
Codeberg's new Privacy Policy went into force on October 2, 2025. The association emailed all users to inform them of the change and published the policy text in its organization repository.
Codeberg doubles membership to 1,208 e.V. members
Codeberg e.V. reports 1,208 total members, with 786 holding active voting rights, 415 supporting members and 7 honorary members. This is nearly twice the 663 members reported in the January 2025 letter.
Codeberg broadens which works its Terms of Use allow
Codeberg e.V.'s General Assembly agreed to replace the rule requiring FSF- or OSI-approved licenses with its own definition of free works. Codeberg said this would officially allow uses it had quietly tolerated, such as CC BY-SA blogs and personal websites, books, artwork, presentation slides, public-domain content and copyleft assets for libre games.
Codeberg's leadership bodies become international
Codeberg e.V.'s Annual Assembly elected a new Presidium for 2025-2027, which appointed a new Executive Board. Both bodies had previously been exclusively German; the Presidium now has members in three European countries, and the Executive Board has three members for the first time, including one from the Netherlands.
Codeberg reports recurring database performance drops
Codeberg said it was struggling with recurring performance degradation in its MariaDB Galera database cluster, with sudden drops every few days, and was investigating the cluster and optimizing Forgejo queries. It had also doubled the RAM of its remaining R730 server by reusing memory from a decommissioned machine, which it said improved performance.
Zig programming language migrates canonical repository to Codeberg
The Zig Programming Language, citing GitHub’s declining engineering quality and unreliable GitHub Actions, makes its GitHub repository read-only and moves its canonical repository to Codeberg. Lead developer Andrew Kelley criticizes GitHub’s engineering culture. The foundation asks GitHub Sponsors donors to move recurring donations to Every.org; GitHub Sponsors had provided more than $170,000 in 2024.
Codeberg launches git-pages-based Pages service
Since December 2025 Codeberg has offered a new Pages service based on git-pages, which it says improves performance and stability and fixes design issues in Pages Server v2. Some features were deprecated, including raw.codeberg.page and direct access to arbitrary repository branches, which Codeberg calls a common abuse vector.
Forgejo v14 deployment leaves some Codeberg CI jobs stuck
After Forgejo v14, released January 15, 2026, was deployed on Codeberg, various CI jobs got stuck in the 'Set up job' phase and did not run, because of an intermittent bug in the new multi-task fetching. Forgejo Runner 12.5.3 and Forgejo v14.0.2 patched the problem.
Gentoo adds Codeberg repository mirror and contribution path
Gentoo announces a Codeberg mirror of the Gentoo repository that accepts pull-request contributions as an alternative to GitHub, as part of a gradual mirror migration. Its end-of-year review cites repeated attempts to force Copilot usage as the reason for the planned move. Gentoo continues to host its primary Git and bug infrastructure itself.
Codeberg publishes its budget publicly for the first time
Codeberg published its 2026 budget plan and said it would publish financial documents in a public repository, after its annual assembly decided to make yearly reports and budgets public. It said it is backed by 1,691 paying members and additional donations, that active members vote on the budget plan, and that cash auditors check spending against the bylaws.
Codeberg members ban 'vibe-coded' projects and pledge no LLM training
Codeberg e.V. members passed two motions. One commits Codeberg not to use user or project code or data to train LLMs; the other, accepted 358 to 144 with 14 abstentions, changes the Terms of Use to prohibit 'vibe-coded' projects. Codeberg said there would be no mass deletion and that moderators would apply the rule using examples rather than an exhaustive list.
Codeberg bans cryptocurrency projects
Alongside its LLM decisions, Codeberg also decided to ban cryptocurrency projects, citing a similar 2023 move by SourceHut. The change was added to its Terms of Use.
Helium browser removes its Codeberg mirrors over the new rules
The Helium browser project removed its repository mirrors from Codeberg, leaving its code only on GitHub, after Codeberg notified users of Terms of Use changes restricting mostly LLM-generated projects and cryptocurrency projects. Its lead developer criticized the rules publicly.
Codeberg sets December 31, 2026 shutdown for Pages v2
Codeberg announced that its unmaintained in-house Pages v2 server will be shut off completely on December 31, 2026. Sites still served the old way, including repositories that never set up a webhook, will stop being served unless their owners migrate to git-pages; Codeberg provides a migration guide and a check tool.
Evidence (59 citations)
D1: User Value Erosion
D2: Business Customer Exploitation
D3: Shareholder Extraction
D4: Lock-in & Switching Costs
D5: Twiddling & Algorithmic Opacity
D6: Dark Patterns
D7: Advertising & Monetization Pressure
D8: Competitive Conduct
D9: Labor & Governance
D10: Regulatory & Legal Posture
Scoring Log (7 entries)
8→8. D1 1→2 (event: storage limits enforced 2025-05-16, AI-crawler slowness 2025-08, DB slowdowns 2025-11, CI stuck 2026-01, July 2026 bans on vibe-coded and crypto projects, Pages v2 shutdown set for 2026-12-31). D5 0→1 (event: heuristic quota allocation from 2025-05; case-by-case enforcement of the 2026 LLM rule). D8 2→1 (recalibration: content-eligibility rules narrow Codeberg's own audience but are not anticompetitive conduct under D8 criteria). D9 3→2 (event: 2025-11 internationalized Presidium/three-member Board, 2026-05 public budgets, 1,691 paying members). Others confirmed. Eras: merged 'Non-Profit Founding' (2019-01-01) and 'Organic Growth' (2021-07-01, no inflection) into 'Volunteer Gitea Host' at 2019-01-01; 'Forgejo Fork Era' re-dated 2022-12-01→2022-12-15 (Forgejo launch); 'Infrastructure Maturity' re-dated 2024-06-01→2024-02-16 (hard fork) and relabeled 'Hard Fork Independence'; current era re-dated 2026-02-19 (assessment date)→2025-05-16 (storage-limit enforcement) and relabeled 'Quotas and Migrations'. All eras re-scored; old early-era D9 of 5 and D10 of 2 recalibrated to 3 and 1 (volunteer, member-governed association; no regulatory conflict). Trajectory improving→stable. D5 evidence floor restored (2 new items). Since Feb 2026: CI regression after Forgejo v14 (Jan), first public budget (May), member votes banning vibe-coded projects and pledging no LLM training plus a crypto-project ban (Jul), Helium mirrors removed (Aug), Pages v2 shutdown announced (Oct); no lawsuits, regulator actions, fees or ads found. Category 'Developer Tools' looks right.
Checked all 23 removed/trimmed candidates: 0 restored, 2 partly restored, 18 confirmed removed, 3 already present in narrowed/correctly dated form. PARTLY RESTORED timeline:update:19: Codeberg News, January 30, 2025 (https://blog.codeberg.org/letter-from-codeberg-looking-into-2025.html), reports later member-management tooling made application decisions one click rather than several minutes, with quicker replies and less bureaucracy; preserve the October 2023 form announcement without backdating those benefits. The added evidence item is PARTLY RESTORED from this same source. PARTLY RESTORED timeline:update:35: Forgejo February 2025 retrospective (https://forgejo.org/2025-02-monthly-update/) confirms an early disruption recovered after a few minutes, not exact 1–2-minute waves or a five-minute maximum. ALREADY PRESENT: organic early growth (D1 narrative; February 2019 report), quotas under v9 on October 16, 2024 (timeline[32]), and the narrower activity-dashboard description (D5 narrative; First Steps documentation). Unsupported remainders of these three items stay out. CONFIRMED REMOVED: alleged Unterwaditzer departure is contradicted by his post about moving TO Codeberg; other dropped causal links, historical figures and universal claims lack qualifying support. Both voting-privacy candidates were checked together; only participant-comment email quotations surfaced, which are excluded. Every candidate has a separate verdict, subclaim description and source/access explanation in work/restore-findings.json. Original URLs and archives, exact terms, named origins and date drift were checked. No score or impact changed; no removals.
Checked 89 original timeline/evidence/milestone items plus 3 alternatives and all prose/identifying fields. ACCEPT items count as verified; individually decided every FIX and REVIEW. Two contradicted details: (1) whole alleged departure by Markus Unterwaditzer, whose September 6 post describes migration from GitHub TO Codeberg (https://unterwaditzer.net/2025/codeberg.html); (2) nearly-15x user growth, contradicted by 379 first-month users and 10,567 in April 2021, about 28x (https://blog.codeberg.org/monthly-report-january-2019.html and https://blog.codeberg.org/monthly-report-april-2021-10k-users.html). Recovered real but miscited figures and moved separately sourced details into supplemental evidence. Historical funding snapshot and unsupported absolutes removed without calling them invented. Checked duplicates: removed D10 hate-response repeat; OSI discussion remains once after dropping unrelated inbound=outbound allegation. Supplemental additions preserve existing claims rather than introduce new developments. Scores and era dates unchanged.
Stripped for Phase 2 re-enrichment