slimtoolkit / slimtoolkit/slim

Was 1.40.2 retagged

Open
#521 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
23.4k
Forks
841
PR merge metrics
No merged PRs in 30d

Description

Expected Behavior

The download for 1.40.2 has the same hash as when it was updated in Homebrew 4 days ago.
The git manual says re-tagging is "the insane thing" to do so it would be good to know this isn't a security problem on the repo.


Actual Behavior

The release says it's from 3 days ago and the Homebrew checksum does not match.


Steps to Reproduce the Problem


Specifications

  • Version: 1.40.2
  • Platform: Any

Contributor guide

Open the contributing guide

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.

Research direction

Start by comparing the 1.40.2 release download hash with the Homebrew checksum and inspect the Git tag history, using the linked Git tagging guidance for context. Determine whether the tag or release was retagged and document whether the mismatch indicates a repository security problem; the issue is resolved when the cause and correct checksum are confirmed.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, go
Domain
release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.