Libraries.io dependent(s)-repos badge doesn't work with go project on GitHub
- Dominant language
- JavaScript
- Stars
- 27.2k
- Forks
- 5.6k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 46
Description
### Are you experiencing an issue with...
shields.io
### 🐞 Description
I tried to create a dependent- and dependents-repos badge via libraries.io, but the platform go doesn't seem to be supported.
On libraries.io it works fine, though:
https://libraries.io/go/github.com%2Fipfs%2Fgo-ipfs
### 🔗 Link to the badge
https://img.shields.io/librariesio/dependents/go/github.com%2Fipfs%2Fgo-ipfs
or
https://img.shields.io/librariesio/dependents/go/github.com/ipfs/go-ipfs
### 💡 Possible Solution
It would be nice if paths like `github.com/ipfs/go-ipfs` would be processed correctly.
Contributor guide
Research direction
Start at the Libraries.io dependents badge endpoint shown in the issue and compare how it handles the encoded and unencoded Go path `github.com/ipfs/go-ipfs` with the working Libraries.io URL. Done means both badge URLs return the expected dependents-repositories badge for the Go project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100