You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on building a dependency graph for golang packages, the proxy.goalng.org do help me a lot, thanks for your great work! Here I have two small questions according to my concerns:
Since we can get mod file from https://proxy.golang.org/<module>/@v/<semver>.mod, which is from source code, do you have any plans for old packages which don't have a mod file?
We can get all versions of a module by https://proxy.golang.org/<module>/@v/list, do you also have an API to query a full package list?
Looking forward to your kind reply, thanks!
The text was updated successfully, but these errors were encountered:
(CC @katiehockman@julieqiu)
Thank you for your kind reply!
Yes, but I have tried this index api https://index.golang.org/index#, it seems I can only get package publishing records after April 10 2019, so I may want a full list of all package id and their versions; Besides, there are a lot of old packages that have no dependency files, I also want an api to get all dependency information, e.g. we can get mod file from https://proxy.golang.org/<module>/@v/<semver>.mod, but for packages that don't have a mod file, it will return an empty mod file, so I was wondering if there is any API to get dependency information for old packages.
Thanks again for your help!
I am working on building a dependency graph for golang packages, the proxy.goalng.org do help me a lot, thanks for your great work! Here I have two small questions according to my concerns:
Since we can get mod file from
https://proxy.golang.org/<module>/@v/<semver>.mod
, which is from source code, do you have any plans for old packages which don't have a mod file?We can get all versions of a module by
https://proxy.golang.org/<module>/@v/list
, do you also have an API to query a full package list?Looking forward to your kind reply, thanks!
The text was updated successfully, but these errors were encountered: