Skip to main content

Security report for spdx.org

SPDX · Technology · N/a

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

Security score

69/100

Risk levelMedium

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

SPDX.dev is the official website for the SPDX project, an open source initiative under the Linux Foundation focused on standardizing software bill of materials (SBOM) and license compliance metadata. The site serves developers and compliance professionals by providing specifications, tools, and community resources. Technically, the site is built on WordPress with integrations of HubSpot marketing and New Relic monitoring, indicating a mature digital infrastructure. Security posture is solid with HTTPS enforced and monitoring scripts in place, though explicit security headers and published security policies are absent. Privacy compliance is weak due to missing privacy and cookie policies. Overall, the site is trustworthy and professional but could improve transparency and compliance documentation.

Scanned

This is an earlier scan of spdx.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
68/ 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. 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 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';…

  3. 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

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

Keep watching spdx.org

This scan found 23 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
85
Security headers
25
Email security
60
DNS health
75
Network security
100
GDPR outside view
68
Average
69

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

SPDX operates as a technology-focused open source project under the Linux Foundation, targeting software developers and compliance teams. Its business model is community-driven standards development, with no direct commercial offerings evident on the site. The project holds a strong market position as a recognized standard for software metadata exchange. Partnerships are primarily within the open source ecosystem. The website content is consistent with the project's mission, though lacks direct contact or business registration details, typical for open source initiatives.

Security posture

The website demonstrates a good security baseline with HTTPS and use of monitoring tools like New Relic. However, it lacks published security policies, incident response contacts, and vulnerability disclosure mechanisms, which are important for transparency and trust. No security headers such as CSP or HSTS were detected, representing an area for improvement. No vulnerabilities or exposed sensitive data were observed. The absence of privacy and cookie policies also indicates compliance gaps.

Recommendations

  1. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  2. Implement and publish a security policy including incident response contacts.
  3. Add security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options.
  4. Provide clear contact information for business and security inquiries.
  5. Establish a vulnerability disclosure program or security.txt file.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
SPDX
Description
SPDX is a project under the Linux Foundation focused on standardizing the way software bill of materials (SBOM) information is shared and communicated. It provides a standardized format for sharing license and security information about software components.
Key services
Standardized SPDX specification, Tools and resources for license compliance, Community collaboration on software metadata
Content quality
good
Branding
consistent

Technology

Stack
WordPress, PHP, JavaScript, Google Tag Manager, HubSpot scripts, FontAwesome, Google Fonts
Frameworks
WordPress, New Relic Browser monitoring
Platforms
Linux Foundation hosting
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security monitoring scripts (New Relic)

Analytics and tracking

Services
HubSpot Analytics, Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
HubSpot, Facebook Pixel
Marketing tools
HubSpot
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional open source project site under Linux Foundation
  2. Content is technology and compliance focused
  3. No privacy or cookie policies explicitly found
  4. No contact emails or phone numbers explicitly listed
  5. Uses multiple third-party marketing and analytics scripts
  6. No security policy or incident response information published
  7. No vulnerability disclosure or security.txt found
  8. Good SSL configuration and HTTPS usage
  9. No WAF or blocking detected
Technical notes

Notes

The website uses WordPress CMS with a modern tech stack including JavaScript libraries, HubSpot marketing tools, and New Relic for performance monitoring. The site loads moderately fast and is mobile optimized. SEO practices are good with proper meta tags and structured data. Accessibility is basic but functional. Hosting details are not explicitly disclosed but likely managed by the Linux Foundation or associated providers. Technical debt appears low with current technologies in use, though security header implementation is lacking.
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. 69/100Medium31 findingsView report
Reviews of this site

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