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

Checksums or signatures for release binaries

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
release, security

Research direction

The issue does not name a source file, test, or release entry point. Start by tracing how this repository publishes release binaries, then determine whether checksums, signatures, or both are expected. Done means downloaded binaries have a corresponding verification artifact and the verification method is clear to users.

Written by the indexing model from the issue text.

Description

It would be great to have a sha256sum or a signature to use to verify the binary when downloaded.

Dominant language
Go
Stars
206
Forks
37
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 docker/compose-switch

All issues in docker/compose-switch

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.