Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Read Assist

Open Beginner friendly
#1,094 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
macos, swift
Domain
content

Research direction

The submission is a request to add Read Assist to the doesitarm app-support list. Start by finding the data file that backs the site's app list in this JavaScript repository, and compare its schema with another Productivity Tools entry. Use the linked build script (scripts/build-app.sh) and the arm64 Mach-O result as evidence of native Apple silicon support. Done when Read Assist appears in the list with the correct category and status, and the site build passes.

Written by the indexing model from the issue text.

Description

The official name of the app

Read Assist

Is there a supported version available on a stable release channel?

Yes — v0.5.0 is the first public source release.

Proposed App Status

✅ Yes, Native Apple Silicon Support

Proposed App Category

Productivity Tools

Related Issue Tracker Links or discussion
An Official App Download Page

https://github.com/ai-nuke/read-assist#try-it-in-a-few-minutes

The supported distribution is currently a local source build. There is no Developer ID-signed or notarized binary download yet.

Full Screenshot with the App and Activity Monitor (if self reporting) or Silicon Info

No Activity Monitor screenshot is attached. Reproducible architecture evidence:

Additional Context

Read Assist targets macOS 14+ on Apple silicon. It is an open-source native SwiftUI/AppKit menu-bar reading companion. The source release is intentionally transparent about its current ad-hoc signing and notarization limitation.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ThatGuySam/doesitarm

All issues in ThatGuySam/doesitarm

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.