macOS / arm64
ClashBar-0.3.6-apple-silicon-no-core.dmg
1.6 MB · v0.3.6 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:9090fa6293773c9dfec6101fb2a82677e2746db3d1f6e77319d407d77a1e65d4
Clients
ClashBar
Architecture labels are derived from asset names. Minimum OS, installation formats and runtime dependencies still require release documentation.
- Installation test
- Not performed
- Project type
- Clients
Upstream release assets
Platform and architecture are based on upstream information. Review release notes, minimum OS and dependencies before installing.
No matching downloads
There are no reviewed files or store listings for the current selection.
macOS / arm64
ClashBar-0.3.6-apple-silicon.dmg
21.2 MB · v0.3.6 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:f25bd38eca4992292535675458a1260c8a5af32b5d7ffd83f3c78869fa48cc19
macOS / x64
ClashBar-0.3.6-intel-no-core.dmg
1.6 MB · v0.3.6 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:0f12e120e192949d47263beb37878cda4801c8f553024a34b115d93cab35f139
macOS / x64
ClashBar-0.3.6-intel.dmg
22.3 MB · v0.3.6 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:f2ab4eaf1720c418e18132ef2d6b0dc5417b89ca2165251a201a7e46f3a57716
Project and release sources
https://github.com/Sitoi/ClashBar (opens in a new tab or window)
Source attribution, checksums and security review are distinct. Unknown details are not marked verified.
From documentation to setup
- Confirm the project and device requirements.
- Use upstream documentation to choose a file or deployment method.
- Understand configuration format, then review runtime logs.
What else should I check?
Is my device guaranteed to work?
No. Device installation tests have not been performed here. Review the project’s OS, privilege and runtime requirements.
Are legacy projects and later forks the same?
No. Project identity and release sources are recorded separately; another maintainer’s software is not presented as an official update of the original project.