| Executor | Platform | Version | sUNC | Detection | Source type | Profile |
|---|---|---|---|---|---|---|
| Xeno | Windows | — | — | — | GitHub repo | View |
| Solara | Windows | 0.1.7c | 59% | Detected | Tracker | View |
| Wave | Windows | NEW-1.5.7 | 100% | Detected | Tracker | View |
| Volt | Windows | 1.3.17.2 | 100% | Could be detected | Tracker + sandbox | View |
| Potassium | Windows | 2.5.3 | 100% | Detected | Tracker + sandbox | View |
| Synapse Z | Windows | 1.0.3.7 | 98% | Detected | Tracker | View |
| SirHurt | Windows | V5.473 | 100% | Detected | Tracker + sandbox + domain | View |
| Real | Windows | 2.7.6 | 100% | Detected | Tracker + sandbox | View |
| Cosmic | Windows | 1.733 | 100% | Detected | Tracker + DevForum + GitBook | View |
| Swift | Windows (claimed) | — | 87% (claimed) | — | Repo description + guide | View |
| Medium | — | — | — | — | None found | View |
| Velocity | Windows | 1.5.1 | 100% | Detected | Tracker + domain scans | View |
| ByteBreaker | Windows | — | 99% (claimed) | — | Website + sandbox + domain | View |
| Fluxus | Windows | — | — | — | Sandbox + domain | View |
| KRNL | Windows | — | — | — | Sandbox + domain | View |
| Electron | Windows (2023 guide) | — | — | — | Archived listing | View |
| Ronin | Windows | 4.1.9 | — | Not marked detected | Tracker | View |
| Volcano | Windows | 3.2.6 | — | — | Tracker + sandbox + domain | View |
| Lumen | — | — | — | — | Sandbox (file only) | View |
Data checked 2026-10-21. A dash means no traceable value was found. "Claimed" means the value comes from a project-controlled description, not a tracker measurement. "Not marked detected" is a third-party field that the tracker explicitly does not verify.
Three Patterns in the Record
Most scores are tracker measurements
Solara, Wave, Volt, Potassium, Synapse Z, SirHurt, Real, Cosmic, Velocity, and Ronin all have version numbers and most have sUNC scores from ScriptBunker or ScriptBlox. Those scores are measurements of function coverage. They are not safety ratings, and the trackers say so themselves.
Some scores are claims, not measurements
Swift's 87% and ByteBreaker's 99% come from repository descriptions and website titles, not from a tracker that ran the sUNC suite. The difference matters: a tracker publishes a test result, a website publishes a description of itself.
Some rows are almost entirely empty
Medium has no record at all. Lumen has one sandbox report about a file that shares the name. Electron has an archived listing and a three-year-old installation guide. Those rows are not failures of the table. They are the table working: showing where the evidence stops.
What this comparison does not do
- This table does not rank executors by safety. No row contains a safety score, because no source reviewed here provides one.
- This table does not treat a blank cell as a negative. A blank cell means no traceable value was found. It does not mean the executor lacks a feature or is unsafe.
- This table does not combine different kinds of evidence into a single number. A tracker measurement and a website claim are not the same kind of record, and the table keeps them separate.
Comparison questions
Why is sUNC the only score in the table?
Because sUNC is the only standardised score that trackers publish consistently for this category. It measures function coverage. It does not measure safety, stability, or detection. Other scores, like Triage's 1–10 behavioral scores, are not comparable across executors because they describe sandbox behavior, not function coverage.
Why do some rows have a version number and no sUNC?
Because the tracker recorded the version but did not publish an sUNC score for that build. Ronin and Volcano are examples. The version number is a record of what the tracker observed. The absence of an sUNC score is a record of what it did not observe.
What does "Could be detected" mean?
It is the phrasing ScriptBlox uses when its upstream detection source marks an executor as potentially detected but does not give a definitive "Detected" flag. It is a warning, not a clearance. The tracker does not guarantee that the executor is undetected.
Why does the table not include prices?
Because prices change and are not a verification signal. ScriptBlox and ScriptBunker record prices for some executors, but a price does not help a reader judge whether a record is traceable or whether a binary is safe. The profile pages record prices where the trackers publish them.
Can I download any executor from this page?
No. This page is a comparison table. It does not host or link to downloads. The Download buttons on the profile pages are placeholders until a verified source is inserted.