Skip to main content

Security report for scipy.org

SciPy · Technology · N/a

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

Security score

67/100

Risk levelMedium

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

SciPy.org is the official website for the SciPy project, a well-established open source scientific computing library for Python. The site provides comprehensive information about the project, its algorithms, and community resources. The project is positioned as a foundational technology in the scientific Python ecosystem, targeting programmers and scientists who require performant and broadly applicable scientific algorithms. The website is professionally designed, mobile optimized, and uses modern technologies such as Hugo for static site generation and Sphinx for documentation. Hosting and DNS are managed via Cloudflare, ensuring good performance and security. Security posture is solid with HTTPS enforced and domain transfer protections in place, though there is room for improvement in security headers and explicit security policies. Privacy compliance is basic with a privacy policy present but lacking a cookie consent mechanism. No direct contact emails or phone numbers are published, consistent with an open source community-driven project. Overall, the site is trustworthy, technically sound, and well-maintained.

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

6 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 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching scipy.org

This scan found 24 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
85
DNS health
80
Network security
100
GDPR outside view
53
Average
67

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

SciPy operates as an important entity in the technology sector, specifically in scientific computing software. Its business model is open source and community-driven, relying on contributions and public development on GitHub. The project has a strong market position as a foundational library extending NumPy, with a broad target audience of scientific programmers. The website reflects a mature project with a long history since 2000 and active community engagement. There are no commercial or advertising elements, emphasizing its non-profit and educational nature. The ecosystem includes related domains for documentation, discussion forums, and conferences, reinforcing its community focus. Strategic partnerships or subsidiaries are not evident, consistent with an open source project structure.

Security posture

The website demonstrates a good security posture with HTTPS enabled and domain registration protections such as clientTransferProhibited status. However, the absence of DNSSEC and security headers like Content-Security-Policy and X-Frame-Options represents an area for enhancement. No vulnerabilities or exposed sensitive data were detected in the HTML content. The lack of published security policies or incident response contacts limits transparency in security governance. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. Overall, the security maturity is moderate to good but could be improved by adopting additional best practices and publishing clearer security documentation.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and enforce security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Add a cookie consent mechanism to comply with GDPR and improve privacy transparency.
  4. Publish a dedicated security policy and incident response contact information to improve trust and readiness.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
SciPy
Description
SciPy provides fundamental algorithms for scientific computing in Python including optimization, integration, interpolation, eigenvalue problems, algebraic equations, differential equations, and statistics. It extends NumPy and offers specialized data structures and performant implementations.
Key services
Scientific computing algorithms, Optimization, Integration, Interpolation, Eigenvalue problems, Algebraic equations, Differential equations, Statistics
Content quality
excellent
Branding
consistent

Technology

Stack
Python, Fortran, C++, Hugo, Sphinx, Bulma CSS, Font Awesome, Cloudflare DNS
Frameworks
Sphinx, Bulma
Platforms
GitHub, Cloudflare
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML

Analytics and tracking

Services
views.scientific-python.org
Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and highly relevant to scientific computing.
  3. No direct contact emails or phone numbers found on the main site.
  4. Privacy and cookie policies exist but cookie consent mechanism is missing.
  5. No explicit security or incident response policies published.
  6. Strong open source community presence and active development.
  7. No advertising or affiliate marketing detected.
  8. Use of modern web technologies and good SEO practices.
Technical notes

Notes

The website uses a modern static site generator (Hugo) combined with Sphinx for documentation, leveraging Bulma CSS and Font Awesome for styling and icons. Hosting is supported by Cloudflare DNS and CDN services, contributing to fast load times and good mobile responsiveness. The site includes multiple CSS files with integrity hashes, indicating attention to security and performance. JavaScript usage is minimal and focused on site functionality and analytics via a scientific-python.org tracking script. SEO is well addressed with meta tags, Open Graph, and Twitter card metadata. Accessibility and navigation are well implemented with clear menus and language options. Overall, the technical infrastructure is robust, modern, and well maintained, supporting a high-quality user experience.
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 scipy.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 scipy.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.