Skip to main content

Security report for osuosl.org

OSU Open Source Lab · Technology · United States

Medium risk. 7 critical or high findings in Security headers and GDPR outside view.

Security score

58/100

Risk levelMedium

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

The OSU Open Source Lab is a nonprofit organization affiliated with Oregon State University, dedicated to advancing open source technologies. It provides a variety of hosting services tailored to open source projects, including general hosting, AARCH64, OpenPOWER, POWER CI, and IBM Z development hosting. The organization targets open source developers, students, and the broader open source community, positioning itself as a key infrastructure provider within the open source ecosystem. The website reflects a medium-sized, well-established entity with a history dating back to 2003. Technically, the website is built using the Hugo static site generator, leveraging modern web technologies such as Font Awesome and Google reCAPTCHA for security. The site is mobile optimized with good SEO practices and moderate performance. However, there is room for improvement in accessibility and security headers implementation. The domain is registered with Porkbun LLC, with consistent WHOIS data matching the organization's identity and no privacy protection, which supports transparency. From a security perspective, the site uses HTTPS and Google reCAPTCHA to protect forms, but lacks DNSSEC and explicit security headers, which are recommended to enhance security posture. No privacy or cookie policies were found, indicating compliance gaps with GDPR and other privacy regulations. Contact information is clearly provided, but no incident response or security policy details are published. Overall, the website is professional, trustworthy, and content-rich, serving its nonprofit mission effectively. Strategic improvements in privacy compliance, security headers, and incident response transparency would further strengthen its security posture and regulatory compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

7 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching osuosl.org

This scan found 21 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. See sample alerts.

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
100
Security headers
15
Email security
75
DNS health
80
Network security
40
GDPR outside view
35
Average
58

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

Technical appendix

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

Business context

Business profile

The OSU Open Source Lab operates as a nonprofit entity under Oregon State University, focusing on providing hosting and development infrastructure for open source projects. Its market positioning is strong within the open source community, leveraging university affiliation as a trust and resource base. The business model is service-oriented, offering managed and unmanaged hosting environments across multiple architectures, including emerging platforms like POWER10 and IBM Z. Revenue streams likely include donations and university funding, with active community engagement through blogs and student employment opportunities. The partnership ecosystem includes Oregon State University and related academic centers. Growth indicators include recent infrastructure upgrades and calls for sustainability funding. Strategic observations highlight the need for diversified funding and infrastructure modernization to maintain long-term viability.

Security posture

The security maturity of the OSU Open Source Lab website is moderate. HTTPS is enforced, and Google reCAPTCHA is used to protect forms, indicating awareness of basic security practices. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options represents potential vulnerabilities. No published security policy or incident response contact reduces transparency and preparedness perception. The lack of privacy and cookie policies also indicates compliance gaps with GDPR and similar regulations. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is adequate for a nonprofit educational site but would benefit from enhancements in DNS security, header implementation, and formalized security documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a comprehensive privacy policy and cookie policy with clear consent mechanisms to improve GDPR compliance.
  4. Develop and publish a security policy and incident response contact information to enhance transparency and readiness.
  5. Regularly audit and update third-party libraries and scripts to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
Oregon State University
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OSU Open Source Lab
Description
A nonprofit organization working for the advancement of open source technologies.
Key services
General Hosting, AARCH64 Development Hosting, OpenPOWER Development Hosting, POWER Continuous Integration (CI), IBM Z Development Hosting
Content quality
good
Branding
consistent

Technology

Stack
Hugo 0.150.1, Font Awesome 6.4.0, Google reCAPTCHA, Pagefind UI
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • Use of Google reCAPTCHA for forms

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. Contact information is clearly provided in the footer.
  4. No security policy or incident response information published.
  5. Technical stack is modern and uses static site generator Hugo.
  6. No analytics or tracking scripts detected beyond Google reCAPTCHA.
  7. Content is focused on open source hosting services and community engagement.
  8. WHOIS data supports legitimacy and long-term operation.
Technical notes

Notes

The website is built on the Hugo static site generator, which provides a fast and secure foundation. It uses modern front-end libraries such as Font Awesome for icons and integrates Google reCAPTCHA for form security. The site is mobile responsive and SEO optimized with proper meta tags and Open Graph data. Hosting details are not explicitly stated, but the domain registrar is Porkbun LLC. Performance is moderate, with asynchronous loading of scripts to improve speed. Accessibility is basic, with room for improvement in ARIA roles and semantic HTML. The lack of CMS reduces attack surface but also limits dynamic content management. Overall, the technical infrastructure is solid but could benefit from enhanced accessibility and security header implementation.
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. 58/100 −6Medium30 findingsView report
  2. 64/100Medium26 findingsView report
Reviews of this site

Share your experience with osuosl.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 osuosl.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.