Zero dependencies
No QEMU, no bundled hypervisor, no third-party runtime. The package graph is empty on purpose, and swift build is the whole build.
Why it matters
Every bundled dependency is something that can break on a macOS update, carry a licence you have to reason about, or need patching on your schedule rather than its own. An empty package graph removes that entire category of problem.
What changes
Without it
- The app ships QEMU or another hypervisor and inherits its update cadence and licensing.
- A host OS update breaks a bundled component you do not control.
With 1VMTool
- Apple's own frameworks plus first-party Swift, and nothing else.
- Nothing to install alongside the app.
What it covers
- No QEMU anywhere in the bundle
- No GPL components to reason about
- Nothing for you to install first
- Built with Swift 6 against an empty package graph
What you get out of it
- One app to install and one thing to update
- A smaller surface for a macOS release to break
Try it on your own Mac
Every screen states its limits before you commit to anything.