YALineo security
Version of November 3, 2026, for YALineo 0.34.4.
This page is for the security teams who assess YALineo before allowing it. YALineo holds no third-party certification (ISO 27001, SOC 2 or other): there is none to show. Instead, this page gives what you can check yourself: what the extension is allowed to do, what it never does, how it is tested at every version, and how to report a flaw to us.
Latest test report
YALineo 0.34.4, on November 3, 2026: 3,380 checks passed out of 3,380, in 9 suites. Every suite passed. 8 suites ran on another state of the code than the report's: their commit is shown under their result.
| Suite | Result | Checks passed |
|---|---|---|
| Unit tests | passedcode c872fd7 | 1,255 / 1,255 |
| FinOps queries on Spark 4 (ANSI) | passedcode c872fd7 | 4 / 4 |
| End to end, Chrome | passed | 747 / 747 |
| Databricks session: anti-CSRF tokens | passedcode c872fd7 | 47 / 47 |
| End to end, Firefox | passedcode c872fd7 | 41 / 41 |
| Booby-trapped metadata attack | passedcode c872fd7 | 95 / 95 |
| Text contrast | passedcode 903065a | 515 / 515 |
| Layout | passedcode af08e7b | 674 / 674 |
| addons-linter (Mozilla) | passedcode c872fd7 | 2 / 2 |
The site reads these figures from the report the test program writes; nobody types them.
What YALineo never does
-
Write to Databricks. Every query goes through a guard before it is sent: a single
SELECTorWITHstatement, no;separator, no writing word (INSERT,UPDATE,DELETE,MERGE,DROP,CREATE,ALTER,GRANT,REVOKE,COPY,OPTIMIZE,VACUUM,CALL,SET,USE...). Quoted text and comments are blanked before the check, and the query must pass both ways a SQL warehouse can read a backslash. Values go in named parameters. Results come back in the response, never throughEXTERNAL_LINKS. The scripts the extension prepares (descriptions, tags, glossary) are text the table owner reviews and runs. - Talk to a YALineo server. There is none. No audience measurement, no automatic error reports, no installation identifier. The only network requests go to the address of your Databricks workspace.
-
Take values out of the Databricks page. In session mode, the extension does not read the session cookie. The headers and the anti-CSRF token that the page script observes stay in the page's memory; the diagnostic holds only their names, counters, the type and method of the calls (the type, taken from the two parts of the path after the API prefix (
/api/2.x/or/ajax-api/2.x/), where an id or an address becomes:id, can include a resource name, such as an endpoint or an app), and the token's shape and age, never its value. -
Run code that comes from the data. No
innerHTML,evalornew Functionin the code: every name, comment or tag read from Databricks is shown as text. The chip lives in a closed Shadow DOM.
What the extension is allowed to do
-
Manifest permissions:
storage,sidePanel,scripting, and optionalnotifications(off by default). Network access to the three Databricks domains only:*.azuredatabricks.net,*.cloud.databricks.com,*.gcp.databricks.com. -
Content policy of the extension pages:
script-src 'self',connect-srclimited to these three domains,object-src 'none',frame-src 'none',base-uri 'none',form-action 'none'. - API paths on an allow list: SQL statements, SQL warehouses, the query and dashboard listings, the lineage of one table, the workspace folder listing (names only, never notebook content), the Genie space listing. Any other address is refused before it is sent, and redirects are refused. The list is checked in three places: the query module (which the command-line preflight tool also uses), the session mode relay and the page script.
- Messages between contexts: the sender of every message is checked; messages that change state are reserved to the extension's pages; a Databricks page can only ask for data from its own workspace.
The data read, kept and sent is detailed in the privacy policy.
The Databricks rights needed
USE CATALOG on system, USE SCHEMA and SELECT on the system tables read only (access, information_schema, billing, lakeflow, query, and compute for the Calculator), CAN USE on a SQL warehouse, nothing else. Session mode, the default, keeps no token. A Databricks personal access token cannot be limited to a scope: attach it to an identity with reduced rights. For the preflight tool in continuous integration, prefer machine-to-machine OAuth with the sql scope only.
How YALineo is tested
At every version, and before every package:
-
Unit tests, including the attack tests of
tests/security.test.mjs: every flaw fixed leaves a test that replays the attack (SQL injection, forbidden API paths, prototype pollution, booby-trapped exports, forged messages...). -
Booby-trapped metadata attack: a fake workspace serves table names, comments, owners, tags and job names loaded with scripts, template injections,
__proto__keys and misleading Unicode characters. The test opens every screen that shows them and checks that no script runs and that no content policy violation is reported. - End-to-end tests in Chrome and Firefox, on a fake workspace that answers like Databricks, and a test of session mode with its anti-CSRF tokens.
- Security pass: review of the changed code (XSS, prototype pollution, SQL injection, API allow list, messages, secret storage), the site's headers and content policy, secret scanning of the history (gitleaks), dependencies, workflows, a STRIDE threat model when a trust boundary changes, and a privacy impact assessment (Quebec Law 25, GDPR).
The test report is produced by a program from the real runs; nobody writes it by hand. The summary of the latest report heads this page on the site.
Dependencies
The extension has no npm dependency at run time and loads nothing from a content delivery network: its code and the Calculator's public price lists are bundled in the package, and it writes in the system's font (Segoe UI on Windows, SF Pro on macOS), as the Databricks workspace does: no font is downloaded.
Check a package
Every version delivered outside a store comes with a SHA256SUMS.txt file. Check the fingerprint before installing: sha256sum -c SHA256SUMS.txt. A package installed from a store (Chrome Web Store, Microsoft Edge Add-ons, addons.mozilla.org) is signed by the store.
Report a flaw
Write to contact@yalineo.com with "Security" in the subject: the version, the browser, the steps to reproduce, and what you could read or do. Include no token, no password and no real data from your workspace. The site's /.well-known/security.txt file gives the same address.