Security
Clear limits for an early macOS alpha.
AndSpace is designed to make local terminal work safer and more understandable, but it is not a sandbox. These notes explain the current alpha security posture and how to verify downloads.
Last updated: May 29, 2026
Unsigned alpha install warning
The current AndSpace public alpha is unsigned prerelease software. macOS may warn that the app cannot be opened normally after download.
This warning is expected for the current prerelease alpha. You may need to right-click the app and choose Open, or allow it from System Settings -> Privacy & Security after the first blocked launch attempt.
Download verification
For v0.1.0-alpha.7, verify the ZIP with: shasum -a 256 AndSpace-v0.1.0-alpha.7-macos.zip. Expected checksum: 2a76eb64f3e56702c22a382c692cb7a59f6c30d4d32cdcb32c2352295fa6bb4e.
Verify the DMG with: shasum -a 256 AndSpace_0.1.0-alpha.7_aarch64.dmg. Expected checksum: f3a05ea81c67a5961f8e2f4f29774468e5a7bb4035f34e2f2bf2528cd32e9d2c.
Command Guard
Command Guard can warn about protected or dangerous commands and can read project guidance from ANDSPACE.md.
Command Guard does not make arbitrary shell commands safe, does not sandbox processes, does not understand every program's side effects, and does not replace user judgment.
Git behavior
AndSpace Git features are read-only in this version. The UI can load status and show visual diff previews.
There are no Git write actions in the UI: no staging, commit, push, pull, checkout, reset, stash, merge, or rebase buttons.
Shell execution
AndSpace does not run hidden shell commands beyond user-triggered app behavior such as starting terminal shells, running selected package scripts, opening external editors, loading read-only Git status/diffs, and launching local AI CLIs when requested.
The app has no auto-update mechanism yet. Future signing and update work should be reviewed separately before public rollout.
Reporting issues
For non-sensitive issues, report problems through GitHub issues. Include the app version, macOS version, install method, and any relevant local diagnostics that you are comfortable sharing.
For sensitive security concerns, do not post secrets or working exploit details publicly. Open a minimal issue asking for a private report path, or use GitHub private vulnerability reporting if it is available on the repository.