Skip to main content

Security report for runcell.dev

Kanaries Data Inc. · Technology · N/a

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

Security score

68/100

Risk levelMedium

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

Runcell.dev is a technology company operated by Kanaries Data Inc. that offers an AI agent designed specifically for Jupyter notebooks. Their product automates code writing, cell execution, debugging, and explanation of results, targeting data scientists and developers who use Jupyter for data analysis and machine learning. The company positions itself as a leading AI assistant in this niche, providing interactive learning modes and autonomous notebook automation. The website is professionally designed, mobile-optimized, and uses modern web technologies including React, Next.js, and Vercel hosting. From a technical perspective, the site demonstrates a mature digital infrastructure with fast performance, good SEO, and accessibility features. It integrates analytics tools such as Google Analytics and Microsoft Clarity for user behavior tracking. Security posture is strong with HTTPS enforced and appropriate security headers present, though there is room for improvement in publishing explicit security policies and incident response plans. The website does not currently implement a cookie consent mechanism, which may impact privacy compliance, especially under GDPR. Contact information is limited to a contact form without direct emails or phone numbers, which could affect user trust and support accessibility. No suspicious or malicious content was detected, and the domain registration details align well with the business claims, indicating legitimacy. Overall, Runcell.dev presents a trustworthy and professional online presence with a strong focus on AI-driven notebook automation. Strategic improvements in privacy compliance and security transparency would further enhance their credibility and user trust.

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

5 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 runcell.dev

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. The full timeline opens with your unlock code.

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
72
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention runcell.dev, from OffSeq Breach.

No leaked records found

Breach holds no records for runcell.dev right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Runcell.dev operates in the AI and data science technology sector, focusing on enhancing Jupyter notebook workflows through automation and AI assistance. Their business model appears to be SaaS-based with free trials and paid subscription plans. The target market includes data scientists, AI researchers, and developers who rely on Jupyter notebooks. The company leverages partnerships with payment processors like Stripe and analytics providers to support operations and marketing. The website content and branding are consistent, supporting a high level of professionalism. Growth indicators include interactive demos and educational content aimed at user engagement. The absence of direct contact details and limited privacy compliance features suggest areas for operational maturity improvement.

Security posture

The website demonstrates a solid security foundation with HTTPS enforced and multiple security headers implemented, reducing common web vulnerabilities. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the lack of a published security policy, incident response plan, or vulnerability disclosure program limits transparency and preparedness. The absence of direct security contact channels may hinder timely incident reporting. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism or explicit GDPR compliance statements. Overall, the security posture is good but could be enhanced by formalizing policies and improving user privacy controls.

Recommendations

  1. Implement a comprehensive cookie consent banner to comply with GDPR and other privacy regulations.
  2. Publish a detailed security policy and incident response plan accessible from the website footer or support pages.
  3. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  4. Provide direct company contact emails or phone numbers for support and security incident reporting.
  5. Enhance privacy compliance statements with explicit GDPR adherence and data retention policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Kanaries Data Inc.
Description
Runcell is an AI agent for Jupyter that automates writing code, executing cells, debugging, and explaining results in real-time.
Key services
AI code generation, Notebook automation, Debugging assistance, Interactive learning mode
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Vercel Analytics, Stripe, Microsoft Clarity
Frameworks
Next.js
Platforms
Vercel
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Microsoft Clarity, Vercel Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Microsoft Clarity
Marketing tools
Microsoft Clarity
Transparency
basic

Site quality

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

Key observations

  1. Professional and modern website design
  2. Clear focus on AI automation for Jupyter notebooks
  3. Use of modern web technologies and analytics
  4. Lack of explicit cookie consent mechanism
  5. No direct contact emails or phone numbers publicly listed
  6. Presence of privacy policy and terms of service pages
  7. No visible security policy or incident response information
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, hosted on Vercel, which supports fast and scalable delivery. Integration with Stripe enables secure payment processing, while analytics tools like Google Analytics and Microsoft Clarity provide user behavior insights. The site is mobile-optimized with responsive design and accessibility considerations. No CMS was detected, indicating a custom or framework-based build. Performance is fast with efficient resource loading and minimal blocking scripts. Technical risks are low, but the absence of some privacy and security documentation could pose compliance risks. Opportunities exist to further modernize privacy management and enhance security transparency.
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 runcell.dev. 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 runcell.dev.

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.