metalsharp / MetalSharp
Run Windows games and Windows applications on MacOS Silicon with MetalSharp. https://www.metalsharpmac.com/
- Stars
- 111 stars
- Forks
- 2 forks
- Language
- C
- License
- AGPL-3.0
- Created
- Apr 26, 2026
- Last push
- Nov 8, 2026
- Updated
- Nov 8, 2026
Why these Tags: an agent read the README and quoted it
- Game launcher from the readme:
| **_GOG Library_** | Download and Play GOG Games |
- macOS app from the description:
Run Windows games and Windows applications on MacOS Silicon with MetalSharp.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 7, 2026: +130 stars in 7 days.
Star History
179 days recorded, May 14, 2026 – Nov 8, 2026 (UTC). Net change +111 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/metalsharp/MetalSharp) Badge
[](https://awesomerepos.com/metalsharp/MetalSharp) Timeline
It gained stars on 7 of the 179 days recorded since May 14, 2026.
Its largest 7 days were Nov 2, 2026 to Nov 8, 2026: 109 stars.
- Created on the Repository Host
- Release v0.78.0
- Release v0.79.0
- Release v0.80.0
- Release v1.0.0
- +5 stars in one day
- Largest star day recorded: +76 stars
- Reached 100 stars, 194 days after it was created
- +25 stars in one day
- Entered the Repository Index: +130 stars in 7 days
- Release v1.1.0
- Latest push
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 8, 2026 – Nov 9, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 9, 2026: new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 9, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 3 tasks for the maintainers of metalsharp/MetalSharp.
Improve the Health Facts of the GitHub repository metalsharp/MetalSharp. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/metalsharp/MetalSharp. A change to the repository can improve each of the 3 items below. Each item gives the measured fact or score, and a task. 1. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-09). Rule: GitHub finds a security policy (SECURITY.md in the repository or in the owner's .github repository). Task: Add SECURITY.md at the root or in .github/. Say which versions get security fixes and how to report a vulnerability privately. If GitHub private vulnerability reporting is on, point to it. Ask me for the contact; do not invent one. 2. A contributing guide Fact: GitHub finds no contributing guide (GitHub, 2026-11-09). Rule: GitHub finds a CONTRIBUTING file in the repository or in the owner's .github repository. Task: Add CONTRIBUTING.md at the root, in docs/, or in .github/. Tell a contributor how to set up the project, run the tests, and propose a change. Use the real commands of this repository (package scripts, Makefile, CI workflows). 3. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-09). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
4 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-08, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
889 commits on the default branch in the last 13 weeks (GitHub, 2026-11-09). Source
-
Yes: Commits in 26 or more of the last 52 weeks
Commits in 28 of the last 52 weeks (GitHub, 2026-11-09). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 13
- 100
- 30
- 196
- 284
- 165
- 192
- 222
- 48
- 33
- 103
- 43
- 0
- 24
- 2
- 4
- 5
- 92
- 95
- 5
- 95
- 99
- 69
- 80
- 83
- 42
- 34
- 88
- 102
Releases
3 of 3 checks-
Yes: A release in the last 365 days
Newest release v1.1.0 on 2026-11-08, 1 day ago. 10 or more releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v1.1.0. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-09). Source
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-09).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
1 of 3 checks-
Yes: A licence
GitHub finds the licence AGPL-3.0. Source
-
No: A contributing guide
GitHub finds no contributing guide (GitHub, 2026-11-09).
-
No: A code of conduct
GitHub finds no code of conduct (GitHub, 2026-11-09).
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
The GitHub dependency graph of this repository names 743 direct packages (scanned on Nov 9, 2026). Packages from 20 other repositories in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 20
-
Cargo: gpui
-
Cargo: globset
- tokio-rs/tokio 34K
Cargo: tokio, tokio-util
- wezterm/wezterm 29K
Cargo: filedescriptor
- gfx-rs/wgpu 18K
Cargo: naga
-
Cargo: smol_str
- hyperium/hyper 16K
Cargo: hyper
- rust-lang/cargo 16K
Cargo: home
- rayon-rs/rayon 13K
Cargo: rayon, rayon-core
-
Cargo: windows, windows-collections, windows-core, windows-future and 18 more
Show all 20
-
Cargo: zed-reqwest
- serde-rs/serde 11K
Cargo: serde, serde_core, serde_derive, serde_derive_internals
- rust-bakery/nom 10K
Cargo: nom
-
Cargo: js-sys, wasm-bindgen, wasm-bindgen-futures, wasm-bindgen-macro and 3 more
- rustls/rustls 7.7K
Cargo: rustls
- briansmith/ring 4.1K
Cargo: ring
- ash-rs/ash 2.4K
Cargo: ash, ash-window
- RustCrypto/hashes 2.3K
Cargo: md-5, sha2
-
Cargo: pbkdf2
-
Cargo: const-oid
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package (checked on Nov 4, 2026). A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 9, 2026: 111 stars, 2 forks, last push Nov 8, 2026, not archived. One of 2 Observations since Nov 8, 2026.