I already use tags for releases. The commit hash is for development. You can check the releases page.
No, it's written with my hands and a lot of coffee. You can check the code. It's open
No PhD, just Win + . and a lot of Rust. But thanks for noticing!
The URL is static. The content is dynamic because I update the Gist. That's how Gist works.
I'm a markdown expert, and i type emojis using Win + . no AI needed.
You're absolutely right. Trust is the real challenge, and I'm just starting to earn it. That's why I keep everything open and plan to add checksum verification. I know it takes time. I'm in it for the long run.
It's open source. Anyone can audit it. You can create your own sources.list, but if you distribute it, you must open the code. Also, "wid info <package_name>" shows the exact URL it downloads from. Example: wid info llvm shows the official GitHub release link.
I use official links and check versions.
I think you should use wid. I already use my own download tool. It's better than winget, choco, and ninite.
No, when I edit the gist, the URL doesn't change. There are 32 packages right now. I've just added Epic Games. I use GitHub Gist.
Actually, it's not static. I'm updating the package list.
I use git regularly. Commits, tags, and releases are all there. If you see something specific I'm doing wrong, feel free to point it out.