Trust
TrailsBI is often run on semantic models whose names and logic are sensitive. These are the facts a security reviewer asks for, with what is not done yet stated as plainly as what is.
What it reads
- Semantic model metadata: TMDL folders,
model.bim,definition.pbism. - Report metadata: PBIR folders, legacy
report.json,definition.pbir. - Power Query (M) expressions and DAX formulas, as text.
What it never touches
cache.abfor any other file holding imported data. Row-level data is never read.- The Power BI service, XMLA endpoints or any tenant API.
- Credentials, gateways or connection secrets.
What it does and doesn't do
- No network calls of any kind, and no telemetry.
- No registry changes and no admin rights. It installs per user with
piporuv, or runs as a single file,trailsbi.pyz, with any Python 3.9 or later. - No dependencies beyond the Python standard library, so there are no third-party packages to pin or audit.
- No writes to your project folders. The only file it creates is the HTML page, where you choose. The one exception is
--embed, which you run on purpose: it writes the hidden TrailsBI table (one.tmdlfile and one line inmodel.tmdl, or one table inmodel.bim), and in a PBIR report the TrailsBI page (one page folder and its entry inpages/pages.json), the visual's files underCustomVisuals/, and the visual's entry indefinition/report.json. Run again, it replaces the table and updates the TrailsBI page'svisual.json. It touches nothing else. - Deterministic, rule-based analysis. No AI service is called, and the same project gives the same findings every time.
What the output contains
One self-contained HTML file. It loads no external scripts, fonts or images, and its Content-Security-Policy blocks network access from the page itself.
It does contain your model's table, column and measure names, the DAX and Power Query, data source addresses, and any filter or slicer values written in the report definition. Treat the page like the project files it came from, and share it where those may go. The same applies to the TrailsBI table that --embed writes.
How releases are built
- Every release is built in GitHub Actions from a public
v*tag in github.com/trailsbi/trailsbi. - It is published to PyPI with trusted publishing, so no PyPI API token is stored anywhere.
- Each GitHub release includes
SHA256SUMS.txtwith the SHA-256 checksums of the wheel, the source package andtrailsbi.pyz. - The code is Apache-2.0 and small enough to read before you approve it.
To verify a download on Windows:
certutil -hashfile trailsbi.pyz SHA256On macOS or Linux:
shasum -a 256 trailsbi.pyzNot done today
- Code signing of release files.
- An SBOM. With no third-party dependencies it would list only TrailsBI itself, but some reviews require one.
- Build provenance attestations for release files.
If your review needs one of them, say so on the feedback page.
Reporting a vulnerability
Use GitHub's private vulnerability reporting: report a vulnerability privately. Please don't open a public issue.
Privacy
TrailsBI collects nothing about you or your reports. The full privacy policy covers the tool, the Power BI visual and this website.