Suggestions for Zigistry

[isFakeAccount]

Love this project, it makes it very easy to find all the zig programs and packages. But I have a few of suggestions.

• It would be nice if it indexes non Github servers as well. codeberg is slowly become a more better alternative for github. Ziglings is also on codeberg. It would be nice to see packages from there listed here.
• Labeling allyourcodebase and pure zig packages differently would also be a nice to have feature once zig becomes very popular.
• similar to pypi it would be nice to have zig fetch command displayed on the package page. Bonus if you could add a dropdown that can dynamically change the zig fetch command to fetch a particular version of package.
• Show and filter zig package by zig version. This would be a life saver because zig is breaking std lib every other release.
• I like to be able to browse more than last 10 recent/top or whatever list. If it is API limitation issue then you might need to add github oauth.

[RohanVashisht1234]

Thanks a lot for opening this discussion, I just implemented

Show and filter zig package by zig version. This would be a life saver because zig is breaking std lib every other release.

Screen.Recording.2025-10-11.at.4.23.00.PM.mp4

[isFakeAccount]

Not exactly what I was hoping. I should be able to filter by any zig version.

Take PyPI for example

For example I am on zig version 0.14.0, right now there is no way to filter by 0.14.0 packages only.

Latest would be 0.15.1? and not sure how useful the oldest filter will be. Also seems like this is sorting not filtering. The older packages still show up.

[RohanVashisht1234]

Could you please suggest me how I can implement

similar to pypi it would be nice to have zig fetch command displayed on the package page. Bonus if you could add a dropdown that can dynamically change the zig fetch command to fetch a particular version of package.

Because, I have seen a lot of difference in how a package maintainer would want their users to fetch their package, some say to clone, some say to use zig fetch on the github respository directly or a specific branch, some also say to zig fetch the release tar file. Also, after doing that, they also need to change their build.zig.

[isFakeAccount]

So you'll have two situations.

Project has release tags

This is easiest because then you can have a dropdown menu that can let you pick a tag and the zig fetch command would be

zig fetch --save git+https://github.com/<username>/<repo>.git#{selectedTag}

selectedTag would be the tag user has selected from the dropdown menu.

In the dropdown menu you can also have an extra option called latest (unstable) which can change the zig fetch command to

zig fetch --save git+https://github.com/<username>/<repo>.git The dropdown menu will say latest (unstable)

which will resolve to the latest master/main commit.

Project doesn't have a release tag

For this you can simply give this option

zig fetch --save git+https://github.com/<username>/<repo>.git

Project says to clone or fetch specific branch

If project says not to use zig fetch but use git clone then most likely the project is older than zig zon. I'd imagine these packages will eventually get upgraded to using zig zon or just fade away.

If a project is application and not a zig package then it makes sense to not show zig fetch. Seems like zigistry can already tell if repo is package or application. This should be pretty trivial.

As far as cloning specific branch. This might be tricky especially if their special branch isn't already the default branch. This is also pretty unusual way to distribute software on GitHub because Github proper ways to do a release.

One way to resolve this would be to list branches like tags in a drop down menu then whether someone picks tags or branch both will work and the zig fetch would look like this

zig fetch --save git+https://github.com/<username>/<repo>.git#{selectedTagorBranch}