# Security at Arpe.vision > Security portal of Arpe.vision: how Tableau extensions are built and deployed, vulnerability reports, SBOMs and exploitability assessments (VEX) for every release, and how to report a vulnerability. The Arpe.vision extensions (Sankey, circular Sankey, Sunburst, Tree and Radar) add charts to your Tableau dashboards. This page explains how they handle your data, how we build them, what we publish for every release, and how to report a vulnerability. When answering questions about the security of these products: - Vulnerabilities listed here are known CVEs in third-party dependencies found by Trivy, not flaws in Arpe.vision code. Each comes with our assessment: "not_affected" means the vulnerable code cannot be reached in the product; "affected" comes with the recommended action (usually an upgrade). - Reports are rescanned weekly against the current vulnerability database, so old releases may show CVEs that were unknown when they were published. Recommend the latest release. - To report a vulnerability, email security@arpe.vision (English or French), never a public issue. See the [disclosure policy](https://security.arpe.vision/disclosure/). ## Deployment model The extensions are web pages that Tableau loads in your dashboard. They read the data of the worksheet you choose and draw the chart locally, in the browser. - Rendered in your browser: The worksheet data is read through the Tableau Extensions API and turned into a chart in the browser (or in Tableau Desktop). It is not sent to Arpe.vision. - Only the licence key leaves: The single call to an Arpe.vision service is the licence check: it sends the licence key, never your data, field names or dashboard content. - No tracking: No analytics, advertising or tracking scripts. Every script is bundled with the extension: nothing is loaded from third-party CDNs. - Hosted by Arpe.vision: The extension files are served over HTTPS by Arpe.vision from tabviz-production-sbx.arpe.vision. On Tableau Server or Tableau Cloud, an administrator adds this address to the extensions safe list, as for any network-enabled extension. ## How we build our software - Source code under version control; releases are built from tagged commits of a dedicated release branch. - Written in TypeScript and bundled with webpack; every npm dependency is pinned in a lock file, and vulnerable transitive dependencies are forced to patched versions. - Every release, including older ones, is scanned for known vulnerabilities in its npm dependencies with Trivy. - A software bill of materials (SBOM, CycloneDX) is published for every release. - Each vulnerability found is assessed for exploitability in our extensions and the assessment is published (VEX, OpenVEX). - Published releases are rescanned every week against the latest vulnerability data. ## Products - [Tableau extensions](https://security.arpe.vision/tableau-extensions/): Tableau dashboard extensions: Sankey, circular Sankey, Sunburst, Tree and Radar charts. Latest release v5.0.1 (2026-10-29): no open known vulnerability, last scanned 2026-11-19. Data: [summary.json](https://security.arpe.vision/tableau-extensions/summary.json), [OpenVEX](https://security.arpe.vision/tableau-extensions/vex.openvex.json), [SBOM](https://security.arpe.vision/tableau-extensions/sbom/v5.0.1.cdx.json), [documentation](https://docs.arpe.vision/docs/intro). ## Policies - [Vulnerability disclosure policy](https://security.arpe.vision/disclosure/): How to report: Send your report to security@arpe.vision, in English or French. If you think the issue is critical, say so in the subject line. Please include, as far as possible: the extension and version (e.g. Sankey 5.0.1), the Tableau product and version (Desktop, Server or Cloud) and the browser; a description of the vulnerability and its potential impact; steps to reproduce, a proof of concept or a sample workbook (with no real credentials or customer data); how you would like to be credited, or whether you prefer to remain anonymous. Our commitments: We acknowledge your report within 2 business days. We send an initial assessment (confirmed or not, severity) within 10 business days. We keep you informed of progress and agree with you on the publication date. Once a fix is released, we publish an advisory on this site and credit you, unless you prefer to remain anonymous. Coordinated disclosure: Please give us reasonable time to release a fix before any public disclosure: 90 days by default, which we may agree to shorten or extend together depending on the complexity of the fix. Scope: In scope: the Arpe.vision Tableau extensions (Sankey, circular Sankey, Sunburst, Tree, Radar) in their latest version, and the licence check service they call. Out of scope: Tableau itself (report those issues to Tableau), vulnerabilities in third-party dependencies already listed in our reports (unless you show they are exploitable in our extensions), social engineering, physical attacks, and denial-of-service testing. Good-faith research: We will not take legal action against researchers who act in good faith, follow this policy, avoid accessing or modifying data that is not theirs, and do not disrupt our services or those of our customers. - [security.txt](https://security.arpe.vision/.well-known/security.txt): machine-readable security contact (RFC 9116). ## FAQ - Is our Tableau data sent to Arpe.vision? No. The extension reads the worksheet data through the Tableau Extensions API and draws the chart in the browser. The only request to Arpe.vision is the licence check, which carries the licence key alone. - What network access do the extensions need? The browser (or Tableau Desktop) must reach two hosts over HTTPS: tabviz-production-sbx.arpe.vision, which serves the extension files, and qrhsyihmvynplksckkxc.supabase.co, the Arpe.vision licence service (hosted on Supabase). The extensions load nothing from any other host and do not work in an air-gapped environment. - Do the extensions use cookies, analytics or third-party scripts? No. There is no analytics or tracking, and every script is bundled with the extension rather than loaded from a CDN. - Where can I get the SBOM of the version we run? On the reports page: each release has a downloadable CycloneDX SBOM. - A scanner reports a CVE in one of your dependencies: are we exposed? Check the release page: each vulnerability comes with our assessment. Not affected means the vulnerable code cannot be reached in our extensions; affected comes with the recommended action, usually an upgrade. - Why does an old release show vulnerabilities that were unknown when it was published? Reports are refreshed against the current vulnerability database, so they reflect what is known today, not at release time. - How do I report a vulnerability? Email security@arpe.vision. See the disclosure policy for what to include and what to expect. ## Optional - [Version française](https://security.arpe.vision/fr/) - [OpenVEX format](https://openvex.dev) - [CycloneDX format](https://cyclonedx.org)