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

add the SHA-256 hash of signing certificate in the README

Open
  • Is something wrong?
#391 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
android
Domain
documentation, security

Research direction

Start with the README, which the issue names as the place for the change. Determine the SHA-256 fingerprint of the signing certificate for the APK users download from GitHub, then add it so users can verify the APK. Done means the README includes the fingerprint; the optional social-media post is outside that README change.

Written by the indexing model from the issue text.

Description

feature request needs triage
Checklist
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

Hi!,
Great app, using it often!
Could you please add the SHA-256 hash of signing certificate in the README so that one can verify the APK?
Also, it's extra but it might help others if you also posted it on a social media so that in case your github got compromised, others can still verify from the SM post 😉
Thank you!

Why do you want this feature?

People downloading directly from source (Github) need to verify the APK via apps like AppVerifier

Additional information

No response

Dominant language
Kotlin
Stars
1k
Forks
98
Avg merge
1d 19h
Merged PRs (30d)
13

Getting set up

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 FossifyOrg/Voice-Recorder

All issues in FossifyOrg/Voice-Recorder

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.