Skip to main content

Security report for scientific-python.org

Scientific Python team · Technology · Iceland

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

Security score

60/100

Risk levelMedium

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

Scientific Python is a community-driven ecosystem focused on scientific computing using Python. It provides coordination documents (SPECs), organizes developer summits, offers development guides, lecture notes, and focuses on improving sparse array capabilities. The website serves as a hub for community participation and volunteer coordination, targeting scientific Python developers, educators, and researchers. The platform is positioned as a niche community resource with a small but dedicated user base. Technically, the site is built using the Hugo static site generator with Sphinx theming, leveraging modern web technologies such as Google Fonts and Font Awesome. The site is performant, mobile-optimized, and well-structured, though accessibility is basic. Security posture is moderate with HTTPS enabled but lacks DNSSEC and security headers. No forms or direct contact emails are present, and privacy compliance is limited with no cookie policy or explicit privacy policy page. Overall, the domain registration is stable and privacy-protected, appropriate for the community nature of the project.

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

8 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 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

    • 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

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

Keep watching scientific-python.org

This scan found 26 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
52
Security headers
30
Email security
70
DNS health
70
Network security
100
GDPR outside view
35
Average
60

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 Scientific Python ecosystem operates as a non-profit community platform focusing on open source scientific computing coordination. Its business model revolves around community engagement, knowledge sharing, and ecosystem governance rather than commercial revenue. The project maintains a strong presence through summits and documentation, fostering collaboration among developers and educators. The absence of direct contact information and commercial elements aligns with its community-driven nature. Partnerships appear limited to open source and community platforms, with no evident commercial subsidiaries or parent companies. Growth indicators include regular summits and active documentation updates. The platform's competitive advantage lies in its focused niche and collaborative approach within the scientific Python ecosystem.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible exposed sensitive data or vulnerable libraries. However, the lack of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security reduces its defense-in-depth. No incident response or security policy information is published, and no vulnerability disclosure or security.txt files are present. The absence of forms reduces attack surface but also limits user engagement channels. Privacy compliance is minimal, lacking cookie consent mechanisms and comprehensive privacy policies. Overall, the security posture is adequate for a static informational site but could be improved to align with best practices and compliance requirements.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  3. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen site security.
  4. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  5. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Scientific Python team
Description
Community developed and owned ecosystem for scientific computing
Key services
SPECs documents for ecosystem coordination, Developer summits, Development guides, Lecture notes, Sparse arrays focus, Community participation and volunteer coordination
Content quality
good
Branding
consistent

Technology

Stack
Hugo static site generator, Google Fonts, Font Awesome, Bulma CSS, PyData Sphinx Theme, JavaScript bundle
Frameworks
Sphinx
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • No exposed sensitive data in HTML
  • No forms detected to collect user input

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a community-driven scientific Python ecosystem coordination platform.
  2. No forms or direct contact emails found on main site.
  3. No explicit privacy or cookie policy pages found, only a code of conduct page.
  4. No security.txt or vulnerability disclosure found.
  5. Social media presence includes GitHub, YouTube, Mastodon, Bluesky, Discourse, and Discord.
  6. No advertising or affiliate marketing detected.
  7. Site uses modern static site generator Hugo and Sphinx theme.
  8. No DNSSEC enabled on domain.
  9. No security headers detected in HTML content.
  10. No phone numbers or physical addresses found.
Technical notes

Notes

The website is built on a modern static site infrastructure using Hugo and Sphinx themes, ensuring fast load times and good mobile responsiveness. The use of Google Fonts and Font Awesome enhances visual appeal. The site lacks dynamic forms, reducing complexity and attack surface. Hosting appears to be managed via NameCheap DNS servers with no DNSSEC enabled. Performance is fast with minimal external dependencies. SEO is supported by proper meta tags and social media cards. Accessibility is basic but could be improved. The technical stack is appropriate for the site's community and informational purpose, with low technical debt and good maintainability.
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

Reviews of this site

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