Skip to main content

Security report for phpstan.org

PHPStan s.r.o. · Technology · N/a

Medium risk. 7 critical or high findings in Email security, Security headers and 1 other check.

Security score

68/100

Risk levelMedium

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

PHPStan s.r.o. operates phpstan.org, a well-established open-source static analysis tool for PHP developers. The company offers a free core product and a premium subscription service called PHPStan Pro, which provides enhanced features such as a web UI and continuous background analysis. The website is professionally designed, mobile-optimized, and provides clear navigation and calls to action, targeting PHP developers and teams aiming to improve code quality and reduce bugs. The business model leverages open-source community engagement supplemented by premium subscriptions, positioning PHPStan as a reputable player in the PHP tooling ecosystem. Technically, the website employs modern web technologies including ES modules, CSS, and minimal JavaScript for analytics via Fathom. Hosting appears to be on Amazon AWS infrastructure, inferred from DNS nameservers. The site loads quickly, is accessible, and SEO optimized with proper meta tags and Open Graph data. However, no CMS or major frameworks are detected, indicating a custom or lightweight static site approach. From a security perspective, the site enforces HTTPS with a good SSL configuration and does not expose sensitive data or vulnerable libraries. However, it lacks DNSSEC, security headers, and published security policies or incident response contacts. Privacy compliance is weak due to the absence of privacy and cookie policies or consent mechanisms. No contact emails or phone numbers are provided, limiting direct communication channels. Overall, the website is trustworthy and professional with a strong community presence but would benefit from enhanced privacy compliance and security transparency to improve user trust and regulatory adherence.

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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

  3. 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 phpstan.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. 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
65
Email security
40
DNS health
70
Network security
100
GDPR outside view
35
Average
68

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

PHPStan holds a strong market position as a leading PHP static analysis tool with a clear open-source foundation and a premium offering. Its competitive advantage lies in early bug detection without requiring tests, legacy code support, and extensions for popular PHP frameworks. Revenue streams likely include subscriptions to PHPStan Pro. The target customers are PHP developers and organizations focused on code quality. The presence of multiple sponsors and partner logos indicates a healthy ecosystem and community support. The company appears to be small but focused, founded in 2017, with no parent or subsidiaries identified. Strategic observations include the importance of expanding privacy and security disclosures to align with enterprise customer expectations and regulatory requirements.

Security posture

The security posture is moderate to strong with HTTPS enforced and no visible vulnerabilities or exposed sensitive data. The lack of DNSSEC and security headers represents a gap that could be exploited in DNS spoofing or clickjacking attacks. Absence of published security policies, incident response contacts, or vulnerability disclosure mechanisms limits transparency and preparedness. Privacy compliance is insufficient, lacking GDPR-related disclosures and cookie consent. The site uses minimal tracking via Fathom Analytics, which is privacy-friendly. Overall, the security culture appears cautious but could be improved by adopting best practices and formal policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Implement and publish security headers such as Content-Security-Policy and X-Frame-Options.
  4. Provide explicit security policy and incident response contact information on the website.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PHPStan s.r.o.
Description
PHPStan is an open-source static analysis tool for PHP that finds bugs in code without requiring tests. It offers premium features via PHPStan Pro, including a web UI and continuous analysis.
Key services
Static code analysis for PHP, Premium web UI and continuous analysis (PHPStan Pro), Extensions for popular PHP frameworks
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript (ES Modules), CSS, HTML5, Fathom Analytics
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Fathom Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected.
  2. No explicit privacy, cookie, or terms of service policies found on the homepage or main navigation.
  3. No contact emails or phone numbers explicitly provided on the homepage.
  4. Strong branding and professional design with clear calls to action.
  5. Use of modern web technologies and analytics with minimal tracking.
  6. Multiple sponsor logos indicate community and business support.
  7. Social media presence includes Twitter, Mastodon, YouTube, and GitHub links.
  8. No forms detected on the homepage for data collection.
  9. No security.txt or vulnerability disclosure information found.
  10. Domain WHOIS data supports legitimacy and business consistency.
Technical notes

Notes

The website is built with modern web standards including ES modules and CSS, hosted on AWS infrastructure as indicated by DNS nameservers. It uses Fathom Analytics for privacy-conscious user tracking. The site is fast, mobile-optimized, and accessible with good SEO practices. No CMS or large frameworks are detected, suggesting a custom or static site approach. The absence of DNSSEC and security headers indicates some technical debt in security hardening. The site does not collect user data via forms on the homepage, reducing attack surface. Overall, the technical infrastructure is solid but could benefit from enhanced security configurations and formal privacy mechanisms.
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 phpstan.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 phpstan.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.