Error: Could not analyze the repository

[cyclone-github]

The Go Report Card for my repository github.com/cyclone-github/hashgen is nearly 2 years out of date and does not reflect the current state of the repository. Upon investigating, it appears that Go Report Card is using an incorrect URL when attempting to fetch / refresh the latest module version which results in an error.

Error when Refreshing Go Report Card:

There was an error processing your request: Could not analyze the repository: could not download repo: could not get latest module version from https://proxy.golang.org/hashgen/@latest

Testing output from currently used URL: https://proxy.golang.org/hashgen/@latest

bad request: invalid escaped module path "hashgen": malformed module path "hashgen": missing dot in first path element

Testing output from corrected URL: https://proxy.golang.org/github.com/cyclone-github/hashgen/@latest

{
  "Version": "v1.0.0",
  "Time": "2024-12-11T01:09:35Z",
  "Origin": {
    "VCS": "git",
    "URL": "https://github.com/cyclone-github/hashgen",
    "Hash": "7c4d425a27f7931856501a7920ee86cc57f67a00",
    "Ref": "refs/tags/v1.0.0"
  }
}

Issue:

This issue is due to Go Report Card using an incorrect URL to fetch / refresh GitHub repositories. This only seems to affect older repositories as new repositories use the correct URL in my testing.
https://proxy.golang.org/{username}/{repo}/@latest

Fix:

Force Fetch / Refresh to use the correct URL:
https://proxy.golang.org/github.com/{username}/{repo}/@latest

[chaseSpace]

me too... what a low-level error! But why no body to fix it? 💢

[cyclone-github]

Devs, this is still a well-known issue affecting many repos. Unfortunately, it makes using goreporter completely useless on affected repos.
Please fix.

[gabrielecabrini]

I have the same issue

There was an error processing your request: Could not analyze the repository: could not download repo: could not get latest module version from https://proxy.golang.org/brainfucker/@latest

but the repository is new, so it doesn't use the correct URL in new repositories