The goal would not be simply to rewrite software in Zig.
Instead, the focus would be building minimal, dependency-light, auditable alternatives to common tools and infrastructure.
Examples:
Does something like this already exist?
Would anyone be interested in contributing?
The name feels kinda silly, but that is not inherently bad.
Simply offering auditing for zig projects, and listing what may be missing, is valuable enough even if it doesn’t develop projects itself.
A quick search and I found 2 organisations, openssf and owasp, that exist to improve OSS security, though I did not check if they offer audits or do any at all, and ofc they are not zig focused.
The two closest orgs that I know are:
Just for context, I’m not trying to imply that you shouldn’t start your own if that’s what you want to do.
I’m all for.
I think the zig ecosystem can use more of this, they would be more stable existences then the projects by individuals who for various reasons can no longer maintain their project.
And in general, we need to build out the zig ecosystem, like rust has done.
As much as I’d like to see some organized effort to bring the ecosystem closer to what Go has, I think the energy is best spent on individual libraries that you need. If a few people/teams do excellent work, the ecosystem will emerge.
Thanks for the references. ZigTools and ZigLibs seem to be the closest examples indeed. I’m trying to explore a slightly different angle focused on minimal, dependency-light software and collaborative ecosystem building.
Yes, I think we need to understand the true essence of Zig Force…
Do you have suggestion for name btw?
how about zigified, ziggins (very similar to ziglings though, but cool) 
“zigged”?
Isn’t it a bit early for creating this?
its never early, we all been zigged, zigified here 
Maybe… Ziggurat? That’s all I got 
For now I’ll keep Zig Force as a temporary working name and focus on defining the project’s direction first .
We can always revisit the name later if the community feels something else fits better.
Oi Lucas.
For project name, my $2c goes to The Zig Nation.
For directions, I would suggest to identify areas where development is needed in order to hopefully drive future efforts. Mobile, documentation, tutorials, etc. Maybe pointing counterparts modules/libs/packages in other languages that would be nice to have in zig.
Thanks Kalapalo
I think that name is awesome, I’ll probably use it. Regarding directions, I’ll probably follow that line, I’m just waiting for more suggestions and feedback from the people who said they were interested in a post on Reddit. By the way, if it makes sense to you, it would be cool to immortalize your suggestion here:
So… not trying to be negative, but “building…alternatives to common tools” sounds like “rewrite software in Zig”, just phrased in a nicer way.
I’d be more supportive of solving problems in existing projects with Zig. Building on the work of others, rather than replacing it. Zig’s interoperability is a key strength other languages do not have.
I think, if I understand correctly, that the goal wouldn’t be 1:1 replacements. But minimal alternatives, with maybe a few tweaks that makes them fit better for narrower scopes, learn from past mistakes without having to worry about legacy, or simply experiment new things.
That’s a fair observation.
The intention isn’t to rewrite software just because “it’s written in Zig”. Reimplementing existing tools is definitely part of the idea, but mainly as a way to learn from existing designs, explore different trade-offs, strengthen the ecosystem and, where it makes sense, build simpler or more auditable alternatives.
I also think Zig’s interoperability is one of its greatest strengths, so Zig Force (perhaps a future Zig Nation) shouldn’t be limited to replacing things. Contributing to existing projects, integrating with existing ecosystems, and building on top of existing work are all valuable directions as well.
I’ll try to clarify this better in the original post and repository documentation.
“The Zig Nation” sounds like “designation” btw 
what about Zigoss
What about doing the “maintain it with Zig” maye building cpython with Zig as one project