Skip to main content

Security report for uppy.io

Transloadit · Technology · N/a

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

Security score

64/100

Risk levelMedium

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

Uppy is an open source JavaScript file uploader developed and maintained by Transloadit. It provides a modular and extensible solution for uploading files from local devices and various remote sources such as Dropbox, Google Drive, Instagram, and more. The platform targets developers and businesses seeking reliable and easy-to-integrate file upload capabilities. Uppy enjoys a solid market position as a community-driven project with commercial backing, supported by endorsements from notable technology communities and publications. Technically, the website leverages modern web technologies including React and Docusaurus for documentation, and integrates the Tus protocol for resumable uploads. Hosting and DNS services are provided by Cloudflare, ensuring robust infrastructure. However, the website suffers from a critical security shortfall due to the absence of a valid SSL certificate and HTTPS support, which significantly impacts its security posture. From a security perspective, while the site avoids known SSL vulnerabilities and uses secure protocols in its backend services, the lack of HTTPS and security headers exposes users to potential risks. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism or GDPR compliance indicators. Contact and incident response information are not publicly available, limiting transparency. Overall, the website demonstrates good content quality, technical sophistication, and business credibility but is hampered by critical security deficiencies. Strategic improvements in SSL deployment, privacy compliance, and contact transparency are recommended to enhance trust and security.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 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

6 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

    • 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 uppy.io

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
90
Security headers
35
Email security
40
DNS health
75
Network security
100
GDPR outside view
43
Average
64

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

Uppy operates as an open source project under Transloadit, focusing on providing a versatile JavaScript file uploader that integrates with multiple cloud storage providers and supports resumable uploads. Its business model combines open source software with commercial support and integration services. The target market includes developers and enterprises requiring robust file upload solutions. Uppy benefits from a strong community and ecosystem, including a dedicated forum and GitHub repository. The project is positioned as a reliable and modern alternative in the file upload space, leveraging partnerships with cloud providers and standards like Tus. Growth indicators include active community engagement and endorsements from technology platforms. The company maintains a medium-sized operation with a focus on technology innovation and developer experience.

Security posture

The current security posture of the Uppy website is moderate but with critical gaps. The absence of a valid SSL certificate and HTTPS support is a major vulnerability that undermines user trust and data security. No security headers such as HSTS or DMARC are configured, and DNS security features like DNSSEC and CAA records are missing. The site does not provide explicit security policies or incident response contacts, limiting its transparency and readiness for security incidents. However, the backend services use secure protocols and avoid known SSL vulnerabilities. The lack of cookie consent and GDPR compliance indicators also points to privacy compliance gaps. Addressing these issues is essential to elevate the security maturity and protect users effectively.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Add DMARC, DNSSEC, and CAA DNS records to enhance email and DNS security.
  4. Establish and publish a comprehensive security policy and incident response contact information.
  5. Introduce a cookie consent mechanism to comply with privacy regulations and improve user transparency.
Technical notes

Notes

The website is built using modern JavaScript frameworks including React and Docusaurus for documentation. It integrates with multiple cloud storage providers via the Companion service and supports resumable uploads using the Tus protocol. Hosting is managed through Cloudflare, providing DNS and CDN services. Performance is moderate with a page load time of approximately 5.6 seconds and a page size of 383 KB. Accessibility and SEO optimizations are good, with proper meta tags and responsive design. However, the lack of HTTPS and security headers represents a significant technical risk. The site uses external analytics (Plausible) and GitHub for community engagement. Overall, the technical infrastructure is solid but requires urgent security enhancements to reduce operational risks.
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. 64/100Medium30 findingsView report
Reviews of this site

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

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.