Skip to main content

Security report for codeberg.org

Codeberg e.V. · Non-profit · Germany

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

64/100

Risk levelMedium

0–100, higher is better. How it is calculated

Codeberg e.V. operates a non-profit, community-driven platform providing free Git hosting and related services to support free and open source software projects. Founded in 2018 and based in Berlin, Germany, Codeberg positions itself as a privacy-respecting alternative to commercial code hosting platforms, emphasizing no tracking, no third-party cookies, and user data protection. The platform is powered by Forgejo, a fork of Gitea, with custom modifications to suit community needs. Technically, the website demonstrates a modern and performant infrastructure using open source technologies such as Forgejo, JavaScript, and SVG graphics. The site is mobile optimized, accessible, and SEO friendly, with fast load times and a clean design. The domain registration is consistent with the organization's history and location, and the site uses HTTPS with a valid SSL configuration. However, DNSSEC is not enabled, and some security headers are missing, which could be improved. From a security perspective, Codeberg shows a strong commitment to privacy and security best practices, including CSRF protection and client transfer domain lock. There is no evidence of tracking or advertising, and the site provides clear channels for abuse reporting. While no formal security policy or vulnerability disclosure page is found, the organization maintains transparency and community engagement. Overall, Codeberg presents a trustworthy, professional, and privacy-conscious platform with a solid technical foundation and a clear mission to support the open source community. Strategic improvements in security headers, DNSSEC, and formal security documentation would further enhance its security posture and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching codeberg.org

This scan found 20 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
75
Security headers
55
Email security
80
DNS health
80
Network security
40
GDPR outside view
53
Average
64

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention codeberg.org, from OffSeq Breach.

Total records
3,320
Employees
0
Customers
3,320
Third parties
0
Weak passwords
7%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for codeberg.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Codeberg e.V. occupies a niche market as a non-profit alternative to commercial Git hosting services, targeting developers, hobbyists, and professionals who value privacy and community governance. Its business model relies on community support, donations, and membership in the non-profit association. The organization demonstrates strong transparency and community involvement, with over 196,000 users and 300,000 projects hosted. Partnerships with Forgejo and integration of services like Woodpecker CI and Codeberg Pages enhance its ecosystem. The absence of advertising and tracking aligns with its privacy-first philosophy, strengthening user trust and loyalty. Growth indicators include active community engagement and a stable user base. The organization’s Berlin location and European hosting provide GDPR compliance advantages.

Security posture

Codeberg exhibits a mature security posture with enforced HTTPS, CSRF token usage, and domain transfer protection. The absence of third-party tracking and cookies reduces attack surface and privacy risks. However, the lack of DNSSEC and missing security headers such as Content-Security-Policy and X-Frame-Options represent areas for improvement. No explicit security policy or vulnerability disclosure page was found, which could limit transparency in incident response. Abuse reporting channels are clearly provided, indicating readiness to handle security incidents. Overall, the platform balances security with usability and privacy, but formalizing security policies and enhancing technical controls would strengthen resilience and compliance.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Develop and publish a formal security policy and vulnerability disclosure program to increase transparency and community trust.
  4. Introduce a cookie consent mechanism to comply with privacy regulations and enhance user awareness.
  5. Provide contact information for a Data Protection Officer or privacy contact to improve GDPR compliance and user confidence.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Codeberg e.V.
Description
Codeberg is a non-profit, community-led organization that aims to help free and open source projects prosper by giving them a safe and friendly home.
Key services
Git hosting, Codeberg Pages, Codeberg Translate, Woodpecker CI, Forgejo API, Status Page
Content quality
excellent
Branding
consistent

Technology

Stack
Gitea (Forgejo fork), JavaScript, Mermaid, SVG, HTML5, CSS3
Frameworks
Forgejo
Platforms
Web
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF token implemented
  • No third-party tracking
  • No cookies for tracking
  • Client transfer prohibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
excellent

Advertising

Transparency
excellent

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a professional non-profit platform for free and open source software hosting.
  2. No tracking or advertising detected, respecting user privacy.
  3. Strong community and transparency focus.
  4. Good technical implementation with modern frameworks and fast performance.
  5. Security posture is good but can be improved with additional headers and DNSSEC.
  6. Clear legal and contact information available.
  7. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on Forgejo, a modern open source Git hosting platform forked from Gitea, customized for Codeberg’s community needs. The front-end uses standard web technologies including HTML5, CSS3, JavaScript, and SVG for graphics. The site is mobile responsive and accessible, with good SEO practices including meta tags and Open Graph data. Performance is fast with minimal external dependencies. The domain is registered with NameSilo, LLC and uses DNS servers from dnsowl.com, though DNSSEC is not enabled. The site uses HTTPS with a valid SSL certificate and includes CSRF protection tokens in forms. No analytics or tracking scripts were detected, aligning with privacy goals. Overall, the technical implementation is solid with room for security enhancements.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 64/100 −1Medium29 findingsView report
  2. 65/100Medium29 findingsView report
Reviews of this site

Share your experience with codeberg.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review codeberg.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.