badgR security tiers for R code, using flowR's static analysis
Local. Your code is analyzed in this browser and never sent anywhere.
How we know

flowR, compiled to JavaScript and WebAssembly, runs in a web worker of this page. The page makes only these requests:

  • its own files: the page, its scripts, and the two WebAssembly parsers,
  • the data of each R package your code loads, from pkgs/<package>.json on this site, so the request names the package but carries none of your code,
  • and only when you ask for it, the GitHub repository or URL you enter. Those requests download and never send anything.

The page's content security policy, which the browser enforces, allows scripts only from this site and forbids form submissions. Uploaded files are read in the browser with the File API, and downloads of reports are created in the browser as well.

The test suite (test/web.test.ts) opens this page in headless Chromium, analyzes uploads, pasted code, and a GitHub repository, and records every request. It fails when a request goes to any host but this site and the GitHub hosts of the requested repository, uses another method than GET, or carries a body.

To check it yourself, open the network tab of your browser's developer tools while you analyze, or go offline once the page has loaded and analyze an upload.

flowR… sigdb… badgR…
or paste R code below
The badges strictest first, from the current policy
    Use the badge in a README or in CI

    Analyze the code in the editor, upload a project, fetch one from GitHub, or start with an example.