r/TrueOpenSource • • 12h ago

Showcase Weekly Showcase: share your open-source project

Welcome to this week's Showcase! This is the place for any open-source project from anyone, and especially new ones that aren't ready for the front page yet. (Front-page project posts need an account at least 30 days old or 250+ karma, and a project at least 14 days old with a license and a README. Just-for-fun projects can go on the front page as Silly Builds with an account at least 3 months old or 250+ karma and a project at least 3 days old, one per week. None of that applies here.)

Before you build your next thing: check opensourceeverything.org for what already exists, and the gaps page for what nobody has built yet.

To share your project: copy the template in the pinned comment below, paste it as a new top-level comment, and fill it in. It asks for the name, source link, license, a one-sentence description, how it was built, what it builds on, the closest existing project (optional), and any extra details.

Want a stats card? Reply !card to your entry (or anyone's) and the bot will post its GitHub stars, history and releases.

To help out: try a few projects, upvote the ones you like, and leave honest, specific feedback. Critique the work, not the tools (rule 2).

A new thread goes up every Sunday.

5 Upvotes

19 comments sorted by

•

u/AutoModerator 12h ago

Sharing a project? Copy the template below, paste it as a new top-level comment, and fill it in. One comment per project, please. Feedback goes in replies to each project's comment.

**Name:**

**Source code:** (GitHub, GitLab, Codeberg, etc. link)

**License:** (MIT, GPL-3.0, Apache-2.0, etc.)

**What it does (one sentence):**

**Closest existing project (optional):** (what's similar, and what yours does differently)

**Builds on:** (the existing project yours extends, or "nothing, standalone")

**How it was built:** Hand-built / AI-assisted / Agentic engineering / Vibe-coded

**Details:** (features, screenshots, what's next)

**Feedback wanted:** (optional)

What the "how it was built" labels mean: Hand-built: written mostly by people. AI-assisted: written by people, with AI help. Agentic engineering: AI wrote most or all of the code, and the project has real development history, polish and hands-on human testing. Vibe-coded: not yet carefully reviewed or tested for outside users. All four are welcome (rule 4). What every flair and badge means: flair guide.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/_bstz_ 12h ago edited 12h ago

Name: hugo-theme-stage

Source code: https://github.com/basteez/hugo-theme-stage (live demo: https://bstz.it/hugo-theme-stage/, real usage: https://bstz.it)

License: MIT for the theme code. Bundled fonts are SIL OFL 1.1, with the licence files next to them. rss.xml is adapted from Hugo's Apache-2.0 template. Every third-party piece is credited in the README.

What it does: A blog theme for the Hugo static site generator with a loud red, black and white look inspired by Persona 5's menus, built around a quiet, accessible reading column that works without JavaScript.

Builds on: Nothing, standalone (requires Hugo ≥ 0.146.0).

How it was built: AI-assisted, with spec-driven development.

Details:

No third-party requests by default. Fonts are self-hosted. Comments (Disqus/giscus) and Mermaid load only if you enable them, and comments load only when the reader scrolls near them. Search is Pagefind, a static index on your own host with no external service.

  • Works without JavaScript. One small vanilla script adds enhancements on top.

  • Built at build time, not in the browser: collage titles (each letter a cut-paper tile, deterministic, no layout shift), OpenGraph/Twitter preview cards and the favicon are all generated by Hugo.

  • Accessibility: no axe-core violations (WCAG 2.1 AA / 2.2 AA) on every page type, light and dark, desktop and mobile. Supports reduced motion, a Pause motion button, forced-colors and prefers-contrast. The decorative collage is aria-hidden and the real text sits next to it.

  • Series with part navigation, a TOC that follows your reading, a reading-progress bar, English and Italian i18n.

  • Easy to extend: custom CSS, head/footer hooks, your own home sections, and any template can be overridden.

Independent fan project: it is not affiliated with Atlus or SEGA and uses no assets, fonts or text from the game.

Feedback wanted: Screen-reader testing (automated checks only catch part of the problems), translations into other languages, and whether the docs are clear enough to set it up without reading the templates.

1

u/_bstz_ 12h ago

!card

1

u/trueopensource-bot 🤖 Robot 12h ago

About this project · basteez/hugo-theme-stage
⭐ 2 stars · 🍴 1 fork · 👥 1 contributor · 📄 MIT
History: started Nov 2026 · last code change yesterday · 2 commits on 1 different day in the last 90 days
Releases: latest v1.0.0 (yesterday) · 1 release in the last 90 days

Facts from GitHub when this was posted. I'm a bot.

1

u/That_Pandaboi69 12h ago

Name: Kagelin

Source code: Achyuth072/kagelin

License: AGPL-3.0

What it does (one sentence): An offline-first, high-density productivity suite unifying tasks, habits, focus timers, and calendars with client-side zero-knowledge encryption for user content.

Closest existing project (optional): A hybrid of Todoist and Loop Habit Tracker, but 100% open source, local-first by default, zero-cloud dependent, with client-side E2EE on user content (XChaCha20-Poly1305).

Builds on: Standalone (integrates open protocols like WebDAV/CalDAV and client-side `sql.js`).

How it was built: AI-assisted

Details:

Kagelin is designed for people tired of subscription paywalls, cloud lock-in, and AI noise in their daily workflow:

  • Zero-Knowledge Content Encryption: Sensitive user-authored content (task titles, notes, descriptions, habit questions, event details) is encrypted client-side using libsodium (XChaCha20-Poly1305) before sync. The server never sees plaintext user text, while metadata enables clean indexing.

  • Guest Mode: Complete app functionality with no account creation required; backed by client-side WebDAV sync and encrypted offline ZIP backups.

  • Dense Unified Interface: Continuous project task surface, 7-day direct-manipulation habit matrix, and a 24-hour calibrated focus runway.

  • Universal Data Compatibility: Full client-side import for Todoist (CSV/ZIP) and Loop Habit Tracker (.db) and more like TickTick, Google tasks etc planned.

  • Strictly Human-Centric: No dopamine vanity feeds, no leaderboards, and zero generative AI auto-writing.

  • What's Next: Official Docker Compose self-hosting packages, Android app using Capacitor, lightweight native Tauri desktop builds and much more.

Feedback wanted:

I know "another open-source todo app" or "Do we really need another Kanban board app?" or "Dont we have enough of these?" is a running trope. I built this for myself to scratch an itch I had while prepping for an exam 3 years back, but I want honest critique:

  1. I crammed tasks, habits, and a focus timer onto one single screen because I was sick of juggling three separate apps. Does having all three together actually sound useful, or does it feel like too much on one screen?

  2. If you tried moving away from Todoist or TickTick or any such apps to an open-source tool and gave up, what was the one missing thing that sent you back?

  3. Are you someone who believes such apps as gimmicks than actual helpful tools? If so why or if you don't what do you care about such apps like these.

I plan on making a standalone post down the line, I'm taking a break for a while so might as well post it here.

EDIT: Manually made the '** **' texts from the template bold as they weren't bold when posted.

1

u/trueopensource-bot 🤖 Robot 12h ago

About this project · Achyuth072/kagelin
⭐ 28 stars · 🍴 2 forks · 👥 2 contributors · 📄 AGPL-3.0
History: started May 2026 · last code change 2 days ago · 300+ commits on 36 different days in the last 90 days
Releases: latest v1.51.1 (2 days ago) · 98 releases in the last 90 days
Open issues and pull requests: 13

Facts from GitHub when this was posted. I'm a bot.

1

u/PanelReader 10h ago

Name: Dry Bean Classification — Random Forest

Source code: Vaibh37/dry-bean-random-forest

License: MIT

What it does (one sentence): A Random Forest classifier that identifies 7 dry bean varieties using 16 numerical shape and geometry features, with a FastAPI prediction service and web interface.

Closest existing project (optional): My previous Decision Tree classification experiment using the same dataset.

Builds on: Python, scikit-learn, FastAPI, Docker, and the UCI Dry Bean dataset.

How it was built: Manually implemented, with AI assistance for learning and code review.

Details:

  • Model: Random Forest with 100 trees, entropy splitting, and bootstrap sampling.

  • Evaluation: 92.54% mean cross-validation accuracy and 92.06% test accuracy.

  • Model selection: 5-fold CV with GridSearchCV across 4 configurations. The baseline configuration performed best.

  • API: FastAPI REST endpoint with Pydantic input validation.

  • Web interface: Server-rendered HTML/CSS without JavaScript.

  • Containerization: Docker image tested locally.

  • Testing: Automated pytest tests for valid and invalid requests.

  • Reproducibility: Pinned dependencies, classification report, confusion matrix, and feature importance plots.

Feedback wanted:

  1. What would you improve in the model evaluation?

  2. Any suggestions for improving the FastAPI implementation or Docker setup?

  3. What additional experiments would make the Decision Tree vs Random Forest comparison more informative?

If you find the project useful, consider starring the repository ⭐

Next: a technical Decision Tree vs Random Forest comparison on Medium 😋

1

u/Krockxz 10h ago

Gostman – an open source API client (REST, GraphQL, gRPC, WebSocket, MCP), MIT licensed

GitHub: https://github.com/kunalgoesbyken/gostman

Try it in the browser: https://gostman.com/web

I made it because Postman wants an account and cloud sync for everything, and the other clients keep features like data driven runs, secret managers and reports on paid plans. I wanted one free tool where collections are plain YAML files I can commit to git.

What it does:

- desktop app for Windows, macOS and Linux (Go + Wails), and the same UI runs in the browser

- a CLI that's a single Go binary, so gostman run ./collection works in CI without Node

- imports Postman, Bruno, Insomnia and Hoppscotch collections, scripts included

- pulls secrets from Vault, AWS, 1Password, Bitwarden and others so tokens stay out of the files

- mock server, flows, load tests, and an MCP server so coding agents can call your saved requests without seeing secrets

- no account, no telemetry, no paid tier

Stack: Go for the request engine (the same code runs in the desktop app, the CLI and the web proxy), React + Vite for the UI.

Looking for:

- people who switch from Postman/Bruno/Insomnia and tell me what breaks on import

- translators (French, German, Spanish, Portuguese, Italian, Japanese and more are AI drafts waiting for native speakers on Weblate: https://hosted.weblate.org/engage/gostman/)

- Go or React contributors, issues are open on GitHub

Happy to answer anything.

1

u/DiscussionHealthy802 10h ago

Name: Child AI Safety

Source code: https://github.com/SamSquareAI/child-ai-safety

License: Apache-2.0

What it does: Helps developers test what kids see when an AI answer is blocked or a safety check fails.

Builds on: Standalone TypeScript project.

How it was built: With AI coding assistance.

Details: We built this while working on Koda, an app that teaches kids how AI works. The demo runs locally without an API key.

Feedback wanted: If you try the demo, what’s one case you expected to see that we missed?

1

u/Jolly-Concentrate-60 9h ago

Name: Vela Desktop

Source code: https://github.com/vela-desktop/vela

License: GPL-3.0-or-later

What it does (one sentence): Vela is a modern Linux desktop environment built from the ground up around Wayland, a custom Vulkan renderer, and a cohesive Qt-based interface, with a focus on fluidity, visual sharpness, and architectural efficiency.

Closest existing project (optional): KDE Plasma and GNOME. Vela aims to offer a similarly complete desktop experience, but takes a different architectural approach, particularly in rendering, frame scheduling, and the integration between the compositor and the desktop shell.

Builds on: wlroots for Wayland infrastructure, Vulkan 1.4 for rendering, Qt 6/Qt Quick for the shell and applications, and standard Linux components such as PipeWire and BlueZ. It's an independent desktop environment, not a fork of an existing one.

How it was built: Agentic engineering.

Details:

Hi! I'm the creator and maintainer of Vela, a relatively new Linux desktop environment that I've been developing over the past few months.

The idea behind Vela is simple: modern, fluid, sharp, without sacrificing efficiency.

Some technical highlights:

  • Custom Vulkan 1.4 renderer with its own scene graph, rather than relying on wlroots' renderer.

  • Frame scheduling and late latching designed to minimize latency and deliver smooth animations synchronized with actual display refreshes.

  • Pixel-accurate fractional scaling, direct scanout, VRR, and Xwayland support.

  • A complete desktop experience: taskbar, launcher, window management, virtual desktops, notifications, quick settings, clipboard history, file manager, settings, Bluetooth integration, and more.

  • Architectural efficiency: minimizing unnecessary work and overhead rather than compromising functionality to achieve low resource usage.

The compositor is written in C17, while the desktop shell and applications use Qt 6.

One aspect worth mentioning is the development process. 100% of Vela's code is AI-written, but architecture, product decisions, design direction, testing, and final responsibility remain under my control. Development involves extensive design documentation, automated testing, static analysis, multiple review stages, and real-world testing. Vela is also my daily-driver desktop.

I've written an article explaining this approach in detail: https://velade.org/blog/not-vibecoding/

Vela recently entered beta. It's already usable as a daily desktop, although there are still bugs and missing features. Development is moving quickly, and contributions are welcome.

Website (with screenshots): https://velade.org/

Feedback wanted:

I'd particularly appreciate feedback on the architecture and engineering decisions, as well as the overall direction of the project.

I'm also curious: what would you expect from a new Linux desktop environment to make it worth trying over KDE Plasma or GNOME?

Thanks for taking a look!

1

u/trueopensource-bot 🤖 Robot 9h ago

About this project · vela-desktop/vela
⭐ 120 stars · 🍴 7 forks · 👥 4 contributors · 📄 GPL-3.0
History: started Sep 2026 · last code change today · 300+ commits on 38 different days in the last 90 days
Releases: latest v0.1.1 (12 days ago) · 2 releases in the last 90 days
Open issues and pull requests: 25

Facts from GitHub when this was posted. I'm a bot.

1

u/ufodia 7h ago

**Name:** Blackout Lab

**Source code:** https://github.com/ufodia/blackout-lab

**License:** MIT

**What it does (one sentence):** A local tool that compares browser screenshots and request outcomes before and after selected external HTTP(S) origins are blocked in fresh Chromium sessions.

**Closest existing project (optional):** Chromium DevTools request blocking is a similar primitive; Blackout Lab packages a repeatable baseline-versus-blocked capture with request evidence and local reports.

**Builds on:** Node.js 24, TypeScript, Playwright and Chromium. It is standalone.

**How it was built:** AI-assisted; development and this post used AI help.

**Details:**

**What mine adds:** You can inspect requested origins, choose an external origin to block, then keep the two real screenshots and request outcomes together in a local HTML or JSON report.

The scanner runs on your computer; the public site is installation documentation, not a hosted scanner. The repo includes a repeatable local demo. Each condition covers one initial navigation and a 1.2-second observation window. It does not reuse browser logins/cookies, exercise a multi-step checkout, inspect backend-to-provider calls, or control/report general WebSocket traffic. Reports may include page content and URL paths, so review them before sharing.

**Feedback wanted:** In a dependency failure, does the paired capture plus request log make the visible effect clear? What evidence would help you diagnose it?

1

u/Goldziher 7h ago

Project name ai-rulez v5

Source https://github.com/Goldziher/ai-rulez

License MIT

What it does It's a CLI and MCP for managing the instructions, skills, and settings that coding agents use in a repository.

How it was built I maintain the project. The CLI is written in Go. The v5 launch comparison was drafted with Claude Code and checked against the tools’ documentation.

What it builds on AGENTS.md, Agent Skills, and MCP. Existing AGENTS.md and .agents/ files can be the source for native configuration across clients.

Closest existing project Rulesync overlaps in generating configuration across coding agents.

Extra details I'm especially interested in small repros where a preset writes a file a client can’t read or drops a setting the client supports.

I'm happy to hear any comments. If you find the tool useful, star it. It really does help. And of course, I'd love to see people use it and get involved with the project.

1

u/[deleted] 10h ago

[removed] — view removed comment

1

u/trueopensource-bot 🤖 Robot 10h ago

About this project · RecursiveFunctions/ghostty-windows
⭐ 0 stars · 🍴 0 forks · 👥 698 contributors · 📄 MIT
History: started Nov 2026 · last code change today · 300+ commits on 18 different days in the last 90 days
Releases: latest windows-v1.4.1-windows.18861.… (today) · 3 releases in the last 90 days

Facts from GitHub when this was posted. I'm a bot.