Security at Arpe.vision
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.
Your data stays in Tableau and your browser
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 extensions
- 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.
Vulnerability reports
Tableau extensions
Tableau dashboard extensions: Sankey, circular Sankey, Sunburst, Tree and Radar charts.
Latest release v5.0.1 (2026-10-29)
No open vulnerability
Methodology
- Dependencies (direct and transitive) are resolved from the source code of each release tag and scanned with Trivy.
- Results reflect the vulnerability database at scan time: an older release may show vulnerabilities disclosed after it was published. Releases are rescanned every week.
- SBOMs are published in CycloneDX format, assessments in OpenVEX format.
- A vulnerability assessed as not affected (the vulnerable code is not reachable in our product) is listed but not counted as open.
Reporting a vulnerability
If you believe you have found a security vulnerability in one of our extensions, please report it privately to security@arpe.vision. Do not open a public issue.
Read our disclosure policyFrequently asked questions
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.
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.No. There is no analytics or tracking, and every script is bundled with the extension rather than loaded from a CDN.
On the reports page: each release has a downloadable CycloneDX SBOM.
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.
Reports are refreshed against the current vulnerability database, so they reflect what is known today, not at release time.
Email security@arpe.vision. See the disclosure policy for what to include and what to expect.