Skip to main content

Security report for getotterwise.com

OtterWise · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

OtterWise is a technology startup launched in 2024 that provides a SaaS platform for tracking code coverage, mutation coverage, and code quality metrics. The platform integrates tightly with GitHub and emphasizes privacy by not requiring access to source code by default. It targets software development teams seeking to improve code health and maintain high-quality standards through automated pull request checks and detailed analytics. The website is professionally designed, mobile-optimized, and uses modern web technologies including Laravel Livewire, Alpine.js, and Tailwind CSS. The technical infrastructure leverages Cloudflare DNS and CDN, Sentry for error monitoring, and Crisp chat for customer support. Security posture is strong with HTTPS enforced and domain transfer protection enabled, though DNSSEC is not enabled and no explicit security policy or incident response information is published. Privacy compliance is good with a comprehensive privacy policy and GDPR considerations, but lacks a cookie consent mechanism despite using Simple Analytics. Overall, OtterWise presents a trustworthy and professional service with a clear business model and strong focus on privacy and developer needs.

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

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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 getotterwise.com

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
75
Security headers
50
Email security
40
DNS health
70
Network security
100
GDPR outside view
53
Average
65

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

OtterWise operates in the niche market of developer tools focused on code quality and coverage analytics. Its competitive advantage lies in its privacy-first approach, allowing teams to benefit from detailed code health insights without exposing source code. The business model is subscription-based with a free tier for public repositories and paid plans for private ones. The platform supports unlimited collaborators and integrates with major CI providers and programming languages, broadening its appeal. The company maintains active engagement through social media and open-source examples on GitHub, enhancing community trust and adoption. Strategic partnerships are not explicitly listed, but integrations with GitHub and use of popular web technologies indicate a modern ecosystem approach. Growth potential is supported by the increasing importance of code quality and security in software development.

Security posture

OtterWise demonstrates a mature security posture for a startup, enforcing HTTPS and using Cloudflare DNS with clientTransferProhibited status to protect domain ownership. The platform avoids collecting personal or usage data and does not access customer source code by default, reducing attack surface. Authentication is managed via GitHub SSO with automatic user removal upon GitHub organization exit, enhancing access control. However, the absence of DNSSEC and lack of published security policies or incident response plans represent areas for improvement. No vulnerabilities or exposed sensitive data were detected in the website content. The use of Sentry for error monitoring and Crisp for support indicates operational security awareness. Overall, the security posture is strong but could benefit from formalized policies and enhanced DNS security.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a formal security policy and incident response plan to increase transparency and trust.
  3. Implement a cookie consent mechanism to comply with privacy regulations given the use of analytics.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Explicitly configure and document security headers such as Content-Security-Policy and X-Frame-Options.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OtterWise
Description
OtterWise is a full-suite code quality reporting platform for type-, mutation- and code-coverage metrics, helping teams ship healthier code faster while prioritizing privacy.
Key services
Code coverage tracking, Code quality reporting, Pull request status checks, API access to coverage data, Browser extension for per-line coverage
Content quality
excellent
Branding
consistent

Technology

Stack
Cloudflare DNS, Sentry (error monitoring), Livewire (Laravel framework component), Alpine.js (for interactivity), Tailwind CSS, Google Fonts (Inter), Crisp chat, Simple Analytics
Frameworks
Laravel (implied by Livewire usage)
Platforms
GitHub (integration), Cloudflare (DNS and CDN)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No code access by default
  • No personal or usage data collected
  • SAML/SSO via GitHub
  • ClientTransferProhibited domain status

Analytics and tracking

Services
Simple Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Simple Analytics
Marketing tools
Crisp chat
Transparency
basic

Site quality

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

Key observations

  1. Website is a modern SaaS platform focused on code coverage and quality metrics.
  2. Strong emphasis on privacy and no code access by default.
  3. Good technical implementation with modern frameworks and tools.
  4. Clear business model with free and paid plans.
  5. Active social media presence on Twitter and GitHub.
  6. No signs of malicious or suspicious activity.
  7. No explicit cookie consent mechanism found despite analytics usage.
  8. WHOIS data is transparent and domain is newly registered.
Technical notes

Notes

The website is built on a modern technology stack including Laravel Livewire for reactive components, Alpine.js for interactivity, and Tailwind CSS for styling. It uses Cloudflare for DNS and CDN services, enhancing performance and security. Error monitoring is handled by Sentry, and customer engagement is supported via Crisp chat. The site is mobile-optimized, fast-loading, and SEO-friendly with comprehensive meta tags and Open Graph data. The absence of a traditional CMS suggests a custom-built platform tailored to the business needs. Performance is rated fast with good accessibility features. Technical risks are minimal, but the lack of DNSSEC and incomplete security header implementation represent potential areas for technical debt and future improvement.
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 getotterwise.com. 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 getotterwise.com.

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.