Welcome to GitHub Discussions — the Vuls community is moving here

[shino]

Hi everyone,

For nearly a decade, the Vuls community has used Slack as its main space for conversation. That Slack workspace is being closed at the end of March 2026, and GitHub Discussions will be our new home for community activity going forward.

How we'll use Issues vs. Discussions

• Issues — for well-scoped, trackable work: bug reports, concrete feature proposals, and other organized tasks that have a clear definition of done.
• Discussions — for everything else: questions, half-formed ideas, design conversations, sharing how you use Vuls, or just casual chat with other users and maintainers.

If you're not sure where something belongs, start it here as a Discussion. We can always convert it into an Issue later if it turns into actionable work.

A heartfelt thank-you to those of you who have already been using GitHub Discussions ahead of the move — your early activity is genuinely appreciated and helps set the tone for the community here.

Original closure announcement

For context, here is the full announcement from @kotakanbe, reproduced verbatim:

---

[Important] Announcement: Closing the Vuls Slack and Transitioning to GitHub Discussions

In 2016, when open-source vulnerability scanners were practically non-existent, I started developing Vuls from scratch through a long process of trial and error. Thanks to the incredible response on GitHub, we opened this Slack channel that same year.

It has been nearly a decade since then. Many of Vuls' core features were born from the discussions held right here. Looking back, I am immensely proud of the community we've built—including the 10 user group meetups we held in Japan, which sparked so many new connections.

To ensure the continued growth of the project, I have decided to close this Slack channel at the end of March 2026 and consolidate our community activities into GitHub Discussions.

Why we are moving:

Knowledge Retention: Under the current Free Plan, message history is only kept for 90 days. This means our precious collective wisdom is constantly disappearing.

Accessibility: Content here is not searchable via the web and is invisible to LLMs (AI). By moving to a public forum, we ensure that solutions are discoverable by everyone—and by the AI tools that developers use every day.

You will, of course, be able to continue asking questions and engaging with the community on GitHub Discussions. Please stay tuned for further details regarding the transition, which will be provided shortly by @MaineK00n.

Vuls is far from over. Development is actively continuing under the leadership of @MaineK00n and @shino, and work on the next-generation "Vuls2"—which is even more lightweight and high-performance—is well underway.

Thank you for your incredible support over the past 10 years. I look forward to seeing you all over at GitHub Discussions!

Best regards,

kotakanbe
Creator of Vuls

---

Looking forward to seeing everyone here. Feel free to introduce yourself or kick off the first conversation below.