Verify remaining RISC-V, Arm A-profile, and Tomcat runtime evidence
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 40/100
Research direction
Start from the original threads #117, #201, and #209 to see what evidence was already gathered. For RISC-V, inspect the pinned formula riscv-gnu-toolchain.rb to identify the source revision, then record the compiler version and confirm ARM64 host architecture. For Tomcat, follow the setup guide and record Tomcat, Java, and macOS versions plus JVM architecture. Done means the riscv-gnu-toolchain, gcc-arm-embedded, and tomcat listings have their evidence fields updated and are no longer left unverified.
Written by the indexing model from the issue text.
Description
Preserve the remaining verification work from the completed listing requests #117, #201, and #209. The listings have been added or updated; these checks are still outstanding.
- RISC-V toolchain: identify the source revision or release in the
arm64_sequoiabottle, record the installed compiler version, and verify ARM64 host architecture. The pinned formula labels the versionmain. Keep the listing unverified until resolved. Original discussion: #117. - GNU Arm A-profile scope: verify the macOS ARM64-hosted package and supported A-profile target separately. The existing listing currently establishes only the
darwin-arm64/arm-none-eabiembedded scope. Official guide. Original discussion: #201. - Tomcat runtime: record successful startup with an ARM64 JDK, including Tomcat, Java, and macOS versions and JVM architecture. Tomcat 10.1 requires Java 11 or later, but package availability alone does not verify this runtime. Listing, Homebrew listing, setup documentation. Original discussion: #209.
Maintainer follow-up: @ThatGuySam. These are evidence gaps, not new claims of tested native support.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ThatGuySam/doesitarm
-
New App Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ThatGuySam/doesitarm#1104 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
ThatGuySam/doesitarm#1101 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ThatGuySam/doesitarm#1100 ·
-
New App Request
Difficulty 1/5 Under an hour Newbie friendliness 82/100
ThatGuySam/doesitarm#1099 · 1 comment ·
-
DynamicHorizonOpenNew App Request
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ThatGuySam/doesitarm#1098 · 1 comment ·
All issues in ThatGuySam/doesitarm
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
521xueweihan/HelloGitHub#3939 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
needs-website-changes
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[Bug] critique requires the detector on native targets, but audit.native.md says it does not applyOpenneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pbakaus/impeccable#1017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day