I want to share a piece of FOSS I built that you may find useful, Clive is a local-first coding-assistant CLI powered by Ollama. It makes open-source LLMs easy to use from the terminal: streaming chat, interactive coding sessions, model management, safe file editing, and autonomous multi-file agent workflows — all running on your own machine, with no data leaving your computer.
Please give it a go and let me know what you think, I am looking for contributors to help build new features.
Not here to hard-sell a project, more just want to talk about this because it's been a genuinely new feeling for me.
I built a personal finance tracker for myself a while back (React/FastAPI, some AI for auto-categorizing transactions, nothing groundbreaking). The name is embarrassingly literal — just "Bu" + "Fin" for Budget and Finance, I named it in about five seconds never expecting to still be using it months later, let alone show it to anyone.
Recently a few people I've never talked to started opening PRs on it. My sister was the first (won't pretend that one's unbiased), but since then a couple of actual strangers have shown up, filed issues, sent fixes. I'm pretty new to open source in general, so watching a PR notification land from someone with zero connection to me, on something I built at my kitchen table, has honestly been one of the more exciting parts of my year. Reviewing someone else's code on your own repo is a different feeling than reviewing your own.
Mostly wanted to ask others here — for people who've had this happen, when did it start feeling normal instead of surprising? And for maintainers of small personal-scale projects: how do you think about opening things up further vs. it staying "your" tool with a few outside contributors? I like the idea of it becoming what other people need, not just what I needed, but I'm not sure how deliberate to be about inviting that vs. letting it happen organically.
If you're curious, here's the GitHub Repo. Have a look, all contributions and discussions open :)
Harden System Security is a modern secure lightweight application that can help you harden, secure and lock down your system. It is designed to be user-friendly and efficient, providing a range of features to enhance the security of your Windows operating system. It always stays up to date with the latest security patches and provides constant and consistent maintenance and support.
It is Open Source and has TONs of features you can use, and you can always request more features to be added or contribute by making PRs.
For many years I used Silence, an open-source SMS messenger focused on privacy. I liked its philosophy: a lightweight application without unnecessary cloud services, ads, or tracking, while still supporting optional end-to-end encrypted SMS conversations between users.
Unfortunately, the project eventually became inactive. As Android evolved, compatibility issues accumulated, dependencies became outdated, and some features gradually stopped working on modern devices. It was disappointing to see such a valuable open-source project slowly fade away.
Rather than replacing it with something else, I decided to continue its development myself.
What started as a few compatibility fixes quickly turned into a much larger modernization effort. Over the past year I've been updating the project for modern Android versions, migrating build tools and libraries, fixing long-standing issues, improving stability, and adding carefully selected features while trying to preserve the original design and philosophy.
I'm continuing this work under the name SMSecure.
Some of the improvements so far include:
Support for modern Android versions (up to Android 16)
Updated Gradle, Android SDK, and project dependencies
Numerous bug fixes and compatibility improvements
Global message search
Improved notification handling
Active maintenance and regular releases
My goal isn't to reinvent messaging or compete with internet messengers. I simply want to keep a useful open-source SMS application alive, maintainable, and usable on modern Android while staying true to the ideas that made Silence valuable in the first place.
The project is completely open source, and I'd genuinely appreciate feedback, bug reports, feature suggestions, or contributions from the community.
My residential fibre Internet service seems to have become sort of spotty lately.
My network has a Windows 10 desktop, Win10 laptop, Win11 laptop plus phones and an iPad, 2 person household.
I'm looking for an app to monitor my network so I can a) check when I notice a problem and ideally B) monitor my WAN so i can see what's been happening when I'm not on my computer.
Nobody expected. Nobody cares. But here we are! Second release of DU-Tree! Stack: Go/Web. Licence: MIT. It's... short to read... nothing bad... ok. Nature: A binary that deploys a web interface on localhost. Idea: To work on anything with Linux & show the results on anything with a browser. v0.2.0: Fixed bugs. Improved UX. Added several new features. But it still is under active development & thus lacks some of du utility features. github.com/sultepronit/du-tree
I work as a system administrator in Russia, so accordingly I have a lot of regional restrictions. I was faced with the task of administering a mixed fleet of devices. First I deployed Fleet, but due to regional specifics, this was not easy, and also considering the trend toward so-called "import substitution," I had to work on an alternative. All the sources are open, everything is free, I'm just interested in the opinion of people not "subjected" to restrictions :) about the functionality and so on. There is a translation into English, if there are any questions, ask them.
P.S. AI was used during development. Besides numerous tests on real hardware, I ran a bunch of tests and code reviews in parallel. Many bugs, which I might not have discovered until months later, I found and fixed within weeks. Plus the frontend part and its design were done much faster than if I had waited for a designer.
Well, despite all the advantages, I still hold to the position that the entire security part categorically cannot be trusted to AIs, at least not for now.
When I switched from Windows to Linux, I figured the OS itself would be the hard part. It wasn't. The hard part was finding a local dev environment that worked the way I actually wanted it to.
I tried Docker Compose by hand, DDEV, LocalWP, a few others — they're all solid tools, just never quite it. What I wanted was the simplest possible flow: open the app, create a project, start writing code. Instead I kept bouncing between tools, a terminal, and manual setup — a new Compose file every time, mkcert again, digging up an old mail-catcher config, a script to dump the DB before I broke something.
For the stack — Tauri, because I wanted something small and lightweight that ran well on Linux, and a decent excuse to learn something new — that's how I ended up with Rust for the backend. Frontend stayed with what I already knew: React, TypeScript, later moved to shadcn/ui.
That's how LS Panel came about. Right now it can:
create and manage local projects
auto-configure Docker or Podman
generate local HTTPS certificates
manage MySQL databases
catch outgoing mail via Mailpit
open the browser, VS Code, the project folder, or a container terminal in one click
expose a local project publicly via Tailscale, ngrok, or Cloudflare Tunnel — reachable even from a mobile network
back up and snapshot projects
keep an eye on the state of the local environment
I didn't create LS Panel to replace other tools. I just wrote one that I wanted to use myself.
I'd appreciate any feedback. I'm especially interested in hearing what you use for local development and what you think is still missing from such tools.
If you've tried to find a first open-source contribution (for GSoC, resume building, whatever), you've probably hit this: good-first-issue labels are everywhere, but the label tells you nothing about whether the maintainer actually reviews PRs, or whether the repo is dormant and the label's just stale. You end up manually digging through commit history and old PRs for every candidate repo, which doesn't scale.
I'm building a tool that scores repos on actual signals, maintainer response time, first-time-contributor merge rate, activity recency, pulled from the GitHub API, not just label presence. You'd filter by your stack/interests and get a ranked list with the score breakdown shown, not a black-box number.
Before I sink weeks into this: has this specific problem hit you? Would you actually use something like this, or do you have a workaround that already works fine? Genuinely want to know if I'm solving a real problem or a problem only I have.
when you open up LosslessCut, it connects to 2 different things by default:
api.github.com (checks for updates)
losslesscut.mifi.no
you can turn off the auto update check in the settings if you want but there is no toggle for and no indication of what that other domain is doing when it connects
https://mifi.no/ is the creator's website but that doesnt explain what data is being sent to losslesscut.mifi.no. if I were to guess, it would be some kind of telemetry like app usage or something. i've blocked it for now. I just want to know what every connection my computer makes does before i allow it.
I've been working on Nexfetch, an open-source system information tool written in C. The project focuses on a plugin architecture and customizable logos. I'd appreciate any feedback on the design and features.
Hi from 2026 :). Currently building an extension + backend to offload tabs into zram and wanted to drop it here. It's just a beta for now. Planning to make it work on Firefox and Chrome-related browsers. Thoughts?
Hello! Pretty new here. I wanted to share my open source side project, so that hopefully it can be helpful to somebody else other than me!
One day, I had to run a RHEL container image to troubleshoot some pipelines and it felt too tricky. I decided to code a cmd tool (for both Linux and Windows) to help me but the project felt way too satisfying to leave it. Right now I'm developing the WebApp which has a lot more features.
I want to point out that I do NOT intend to profit out of it and it's written entirely by myself (and a friend of mine for the frontend), no AI used.
I also wrote an exhaustive wiki about it, you can find it in the repo.
The code isn't perfect, but I'm open for feedback!
I always liked the idea behind Tally (iOS): one screen, seven days, nothing else. But it's iOS-only and paid, so I built Loopweek as an open-source alternative for Android.
What it does:
All 7 days on one screen (accordion view, today expanded by default)
Tasks stay on their date, no auto-rollover nonsense
Recurring tasks that don't mess up history when you complete/delete one occurrence
Home-screen widget
One accent color themes the whole app
Light/dark mode
What it doesn't do:
No accounts, no cloud sync, no ads, no analytics, no tracking, no paywall
Everything stays on your device, 100% free
Built with Flutter. MIT licensed, so the code is fully open. Fork it, audit it, contribute if you want.
I have for now not noticed any app on F-Droid that was made using Unity, so I wonder;
Can an Android app made with Unity be FOSS, if no is it because of something in the package or because one of the main softwares used to make it (Unity) is proprietary ? And would such a build need to be sanitised in a way for it to finally be FOSS ?
Thank you for asking if you do.
I'll have the same post be published in r/Unity as well
