Built an open-source frontend security scanner with a desktop GUI (ShieldEye SurfaceScan) 🔍🛡️
Hi all,
over the last months I’ve been tinkering with a side project in my spare time and it slowly grew into something that feels usable, so I decided to put it out there.
It ended up as
**ShieldEye SurfaceScan**
– an open-source desktop app that looks at the
**frontend attack surface**
of a site. 🔍
The idea is simple: you point it at a URL, it spins up a headless browser, lets the page execute its JavaScript and then tries to make sense of what it sees. It looks at HTML and noscripts, guesses which third‑party libraries are in use, checks HTTP security headers and cookies, and then puts everything into a few views: dashboard, detailed results and some basic analytics. If you have Ollama running locally, it can also add a short AI‑generated summary of the situation, but that part is completely optional. 🤖
Under the hood it’s a small stack of services talking to each other:
\- a GTK desktop GUI written in Python,
\- an API in Node + TypeScript + Express,
\- a Playwright-based worker that does the actual page loading and analysis,
\- PostgreSQL, Redis and MinIO for data, queues and storage.
Even though I mainly use it through the GUI, there is also a JSON API behind it (for scans, results and analytics), so it can be driven from noscripts or CI if someone prefers to keep it headless.
In my head the main audience is:
\- people learning web security who want something to poke at the frontend surface of their own projects,
\- developers who like a quick sanity check of headers / JS / deps without wiring a whole pipeline,
\- anyone who enjoys self‑hosted tools with a native-style UI instead of another browser tab. 🖥️
The code is on GitHub (MIT‑licensed):
https://github.com/exiv703/ShieldEye-SurfaceScan
There’s a README with a bit more detail about the architecture, Docker setup and some screenshots.
If you do take it for a spin, I’d be interested in any feedback on:
\- how the GUI feels to use (what’s confusing or clunky),
\- what kind of checks you’d expect from a tool focused on the frontend surface,
\- anything that breaks on other systems (I mostly run it on Linux 🐧).
Still treating this as a work in progress, but it’s already at the point where it can run real scans against your own apps and show something useful.Hi all,
over the last months I’ve been tinkering with a side project in my spare time and it slowly grew into something that feels usable, so I decided to put it out there.
It ended up as **ShieldEye SurfaceScan** – an open-source desktop app that looks at the **frontend attack surface** of a site. 🔍
The idea is simple: you point it at a URL, it spins up a headless browser, lets the page execute its JavaScript and then tries to make sense of what it sees. It looks at HTML and noscripts, guesses which third‑party libraries are in use, checks HTTP security headers and cookies, and then puts everything into a few views: dashboard, detailed results and some basic analytics. If you have Ollama running locally, it can also add a short AI‑generated summary of the situation, but that part is completely optional. 🤖
Under the hood it’s a small stack of services talking to each other:
\- a GTK desktop GUI written in Python,
\- an API in Node + TypeScript + Express,
\- a Playwright-based worker that does the actual page loading and analysis,
\- PostgreSQL, Redis and MinIO for data, queues and storage.
Even though I mainly use it through the GUI, there is also a JSON API behind it (for scans, results and analytics), so it can be driven from noscripts or CI if someone prefers to keep it headless.
In my head the main audience is:
\- people learning web security who want something to poke at the frontend surface of their own projects,
\- developers who like a quick sanity check of headers / JS / deps without wiring a whole pipeline,
\-
Hi all,
over the last months I’ve been tinkering with a side project in my spare time and it slowly grew into something that feels usable, so I decided to put it out there.
It ended up as
**ShieldEye SurfaceScan**
– an open-source desktop app that looks at the
**frontend attack surface**
of a site. 🔍
The idea is simple: you point it at a URL, it spins up a headless browser, lets the page execute its JavaScript and then tries to make sense of what it sees. It looks at HTML and noscripts, guesses which third‑party libraries are in use, checks HTTP security headers and cookies, and then puts everything into a few views: dashboard, detailed results and some basic analytics. If you have Ollama running locally, it can also add a short AI‑generated summary of the situation, but that part is completely optional. 🤖
Under the hood it’s a small stack of services talking to each other:
\- a GTK desktop GUI written in Python,
\- an API in Node + TypeScript + Express,
\- a Playwright-based worker that does the actual page loading and analysis,
\- PostgreSQL, Redis and MinIO for data, queues and storage.
Even though I mainly use it through the GUI, there is also a JSON API behind it (for scans, results and analytics), so it can be driven from noscripts or CI if someone prefers to keep it headless.
In my head the main audience is:
\- people learning web security who want something to poke at the frontend surface of their own projects,
\- developers who like a quick sanity check of headers / JS / deps without wiring a whole pipeline,
\- anyone who enjoys self‑hosted tools with a native-style UI instead of another browser tab. 🖥️
The code is on GitHub (MIT‑licensed):
https://github.com/exiv703/ShieldEye-SurfaceScan
There’s a README with a bit more detail about the architecture, Docker setup and some screenshots.
If you do take it for a spin, I’d be interested in any feedback on:
\- how the GUI feels to use (what’s confusing or clunky),
\- what kind of checks you’d expect from a tool focused on the frontend surface,
\- anything that breaks on other systems (I mostly run it on Linux 🐧).
Still treating this as a work in progress, but it’s already at the point where it can run real scans against your own apps and show something useful.Hi all,
over the last months I’ve been tinkering with a side project in my spare time and it slowly grew into something that feels usable, so I decided to put it out there.
It ended up as **ShieldEye SurfaceScan** – an open-source desktop app that looks at the **frontend attack surface** of a site. 🔍
The idea is simple: you point it at a URL, it spins up a headless browser, lets the page execute its JavaScript and then tries to make sense of what it sees. It looks at HTML and noscripts, guesses which third‑party libraries are in use, checks HTTP security headers and cookies, and then puts everything into a few views: dashboard, detailed results and some basic analytics. If you have Ollama running locally, it can also add a short AI‑generated summary of the situation, but that part is completely optional. 🤖
Under the hood it’s a small stack of services talking to each other:
\- a GTK desktop GUI written in Python,
\- an API in Node + TypeScript + Express,
\- a Playwright-based worker that does the actual page loading and analysis,
\- PostgreSQL, Redis and MinIO for data, queues and storage.
Even though I mainly use it through the GUI, there is also a JSON API behind it (for scans, results and analytics), so it can be driven from noscripts or CI if someone prefers to keep it headless.
In my head the main audience is:
\- people learning web security who want something to poke at the frontend surface of their own projects,
\- developers who like a quick sanity check of headers / JS / deps without wiring a whole pipeline,
\-
anyone who enjoys self‑hosted tools with a native-style UI instead of another browser tab. 🖥️
The code is on GitHub (MIT‑licensed):
https://github.com/exiv703/ShieldEye-SurfaceScan
There’s a README with a bit more detail about the architecture, Docker setup and some screenshots.
If you do take it for a spin, I’d be interested in any feedback on:
\- how the GUI feels to use (what’s confusing or clunky),
\- what kind of checks you’d expect from a tool focused on the frontend surface,
\- anything that breaks on other systems (I mostly run it on Linux 🐧).
Still treating this as a work in progress, but it’s already at the point where it can run real scans against your own apps and show something useful.
https://redd.it/1ptbnko
@r_opensource
The code is on GitHub (MIT‑licensed):
https://github.com/exiv703/ShieldEye-SurfaceScan
There’s a README with a bit more detail about the architecture, Docker setup and some screenshots.
If you do take it for a spin, I’d be interested in any feedback on:
\- how the GUI feels to use (what’s confusing or clunky),
\- what kind of checks you’d expect from a tool focused on the frontend surface,
\- anything that breaks on other systems (I mostly run it on Linux 🐧).
Still treating this as a work in progress, but it’s already at the point where it can run real scans against your own apps and show something useful.
https://redd.it/1ptbnko
@r_opensource
Reddit
From the opensource community on Reddit: Built an open-source frontend security scanner with a desktop GUI (ShieldEye SurfaceScan)…
Explore this post and more from the opensource community
A simple CLI file encrypter in Go
GitHub: https://github.com/pingminus/SafeGuard
A simple CLI file encryption tool in Go with AES-GCM, XOR, and Caesar ciphers. Great for learning and experimentation. Not for high-security use. Contributions and improvements are welcome! I originally started writing it in C++, but ran into library issues, so I switched to Go.
https://redd.it/1pt9q0f
@r_opensource
GitHub: https://github.com/pingminus/SafeGuard
A simple CLI file encryption tool in Go with AES-GCM, XOR, and Caesar ciphers. Great for learning and experimentation. Not for high-security use. Contributions and improvements are welcome! I originally started writing it in C++, but ran into library issues, so I switched to Go.
https://redd.it/1pt9q0f
@r_opensource
GitHub
GitHub - pingminus/SafeGuard: CLI Encryption tool written in Go
CLI Encryption tool written in Go. Contribute to pingminus/SafeGuard development by creating an account on GitHub.
Struggling with SEO in Vite + React FOSS. Am I screwed?😭😭
Hello everyone,
I hope at least one of you can help me...
I maintain a FOSS Vite React project that’s still pre-v1 and needs a lot of work, and I want it to be discoverable so new devs can find it and help implement the long list of features needed before the first proper release, but I’m running into serious SEO headaches and honestly don't know what to do.
I’ve tried a bunch of approaches in many projects like react-helmet (and the async version, Vite SSG, static rendering plugins, server-side rendering with things like vite-plugin-ssr, but I keep running into similar problems.
The head tags just don’t want to update properly for different pages - they update, but only after a short while and only when JS is enabled. Meta tags, noscripts, denoscriptions, and whatnot often stay the same or don't show the right stuff. Am I doing it wrong?
What can I do about crawlers that don’t execute JavaScript? How do I make sure they actually see the right content?
I’m also not sure if things like Algolia DocSearch will work properly if pages aren’t statically rendered or SEO-friendly.
I'm 100% missing something fundamental about SEO in modern React apps because many of them out there are fine - my apps just aren't.🥲
Is it even feasible to do “good” SEO in a Vite + SPA setup without full SSR or am I basically screwed if I want pages to be crawlable by non-JS bots?😭
At this point, I'll happily accept any forms of advice, experiences, or recommended approaches — especially if you’ve done SEO for an open-source project that needs to attract contributors.
I just need a solid way to get it to work because I don't want to waste my time again in another project.😭😭😭😭
https://redd.it/1pta5ql
@r_opensource
Hello everyone,
I hope at least one of you can help me...
I maintain a FOSS Vite React project that’s still pre-v1 and needs a lot of work, and I want it to be discoverable so new devs can find it and help implement the long list of features needed before the first proper release, but I’m running into serious SEO headaches and honestly don't know what to do.
I’ve tried a bunch of approaches in many projects like react-helmet (and the async version, Vite SSG, static rendering plugins, server-side rendering with things like vite-plugin-ssr, but I keep running into similar problems.
The head tags just don’t want to update properly for different pages - they update, but only after a short while and only when JS is enabled. Meta tags, noscripts, denoscriptions, and whatnot often stay the same or don't show the right stuff. Am I doing it wrong?
What can I do about crawlers that don’t execute JavaScript? How do I make sure they actually see the right content?
I’m also not sure if things like Algolia DocSearch will work properly if pages aren’t statically rendered or SEO-friendly.
I'm 100% missing something fundamental about SEO in modern React apps because many of them out there are fine - my apps just aren't.🥲
Is it even feasible to do “good” SEO in a Vite + SPA setup without full SSR or am I basically screwed if I want pages to be crawlable by non-JS bots?😭
At this point, I'll happily accept any forms of advice, experiences, or recommended approaches — especially if you’ve done SEO for an open-source project that needs to attract contributors.
I just need a solid way to get it to work because I don't want to waste my time again in another project.😭😭😭😭
https://redd.it/1pta5ql
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Leaving the Big Tech behind
Doctorow has been all over the media on both sides of the Atlantic.
Yes, much has gone to shit. People put up with no end of it, because of the Sunk Cost Fallacy.
Surely, now is the time to challenge that fallacy, on the brink of huge tech downturn.
Federated social media, privacy focused mobile devices, the right to repair, open source operating systems. All these are within the grasp of anyone who is prepared to make a little effort. Secure, paid mail services abound.
But there needs to be a concerted, off-ramp from things like Facebook. It's no use signing up to Mastodon and finding literal crickets.
Is anyone up for creating a welcome committee, so people might actually find a friendly face if they take the plunge into Mastodon or Pixelfed?
https://redd.it/1pth83u
@r_opensource
Doctorow has been all over the media on both sides of the Atlantic.
Yes, much has gone to shit. People put up with no end of it, because of the Sunk Cost Fallacy.
Surely, now is the time to challenge that fallacy, on the brink of huge tech downturn.
Federated social media, privacy focused mobile devices, the right to repair, open source operating systems. All these are within the grasp of anyone who is prepared to make a little effort. Secure, paid mail services abound.
But there needs to be a concerted, off-ramp from things like Facebook. It's no use signing up to Mastodon and finding literal crickets.
Is anyone up for creating a welcome committee, so people might actually find a friendly face if they take the plunge into Mastodon or Pixelfed?
https://redd.it/1pth83u
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Ephemera: an open-source, self-hosted SSH Certificate Authority built on native OpenSSH (seeking architecture review)
Hey everyone,
I’ve been working on a self-hosted project exploring a different approach to SSH access and sudo control, without cloud dependencies or SSH proxies.
Ephemera is an air-gap-friendly SSH Certificate Authority built entirely on native OpenSSH and PAM primitives. The core idea is to eliminate long-lived trust rather than rotate it.
Repo:
https://github.com/Qarait/ephemera
Documentation:
https://qarait.github.io/ephemera/index.html
At a high level, Ephemera:
1-Replaces static SSH keys with short-lived certificates (minutes)
2-Requires WebAuthn hardware-backed presence for cert issuance
3-Implements Just-in-Time sudo: privileged commands pause until explicitly approved
4-Uses policy-driven RBAC (OIDC groups, IP ranges, time windows)
5-Produces tamper-evident, hash-chained audit logs
6-Supports encrypted, sovereign recovery via Shamir secret sharing
7-Runs fully self-hosted, Dockerized and air-gap capable
Explicit non-goals (intentional design choices):
No MITM SSH proxy, direct OpenSSH connections only; no traffic interception layer.
No custom SSH protocol, relies exclusively on upstream OpenSSH semantics.
No always-on root access, all privilege escalation is time-bound and explicitly approved.
Prefer native OpenSSH and PAM primitives over agents, sidecars or long-running daemons.
https://redd.it/1pthmwx
@r_opensource
Hey everyone,
I’ve been working on a self-hosted project exploring a different approach to SSH access and sudo control, without cloud dependencies or SSH proxies.
Ephemera is an air-gap-friendly SSH Certificate Authority built entirely on native OpenSSH and PAM primitives. The core idea is to eliminate long-lived trust rather than rotate it.
Repo:
https://github.com/Qarait/ephemera
Documentation:
https://qarait.github.io/ephemera/index.html
At a high level, Ephemera:
1-Replaces static SSH keys with short-lived certificates (minutes)
2-Requires WebAuthn hardware-backed presence for cert issuance
3-Implements Just-in-Time sudo: privileged commands pause until explicitly approved
4-Uses policy-driven RBAC (OIDC groups, IP ranges, time windows)
5-Produces tamper-evident, hash-chained audit logs
6-Supports encrypted, sovereign recovery via Shamir secret sharing
7-Runs fully self-hosted, Dockerized and air-gap capable
Explicit non-goals (intentional design choices):
No MITM SSH proxy, direct OpenSSH connections only; no traffic interception layer.
No custom SSH protocol, relies exclusively on upstream OpenSSH semantics.
No always-on root access, all privilege escalation is time-bound and explicitly approved.
Prefer native OpenSSH and PAM primitives over agents, sidecars or long-running daemons.
https://redd.it/1pthmwx
@r_opensource
GitHub
GitHub - Qarait/ephemera: Zero-Trust SSH CA
Zero-Trust SSH CA. Contribute to Qarait/ephemera development by creating an account on GitHub.
Leaving the Big Tech behind
Doctorow has been all over the media on both sides of the Atlantic.
Yes, much has gone to shit. People put up with no end of it, because of the Sunk Cost Fallacy.
Surely, now is the time to challenge that fallacy, on the brink of huge tech downturn.
Federated social media, privacy focused mobile devices, the right to repair, open source operating systems. All these are within the grasp of anyone who is prepared to make a little effort. Secure, paid mail services abound.
But there needs to be a concerted, off-ramp from things like Facebook. It's no use signing up to Mastodon and finding literal crickets.
Is anyone up for creating a welcome committee, so people might actually find a friendly face if they take the plunge into Mastodon or Pixelfed?
https://redd.it/1pth7ak
@r_opensource
Doctorow has been all over the media on both sides of the Atlantic.
Yes, much has gone to shit. People put up with no end of it, because of the Sunk Cost Fallacy.
Surely, now is the time to challenge that fallacy, on the brink of huge tech downturn.
Federated social media, privacy focused mobile devices, the right to repair, open source operating systems. All these are within the grasp of anyone who is prepared to make a little effort. Secure, paid mail services abound.
But there needs to be a concerted, off-ramp from things like Facebook. It's no use signing up to Mastodon and finding literal crickets.
Is anyone up for creating a welcome committee, so people might actually find a friendly face if they take the plunge into Mastodon or Pixelfed?
https://redd.it/1pth7ak
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Open-source React Native app: how do you share Android test builds?
I’m contributing to an open-source React Native app built with Expo and EAS.
What’s the usual approach for sharing Android test builds with contributors outside the Play Store?
Do people generally prefer APKs, AABs, or Expo-hosted artifacts?
Interested in hearing what works well in open-source projects.
https://redd.it/1ptk6uu
@r_opensource
I’m contributing to an open-source React Native app built with Expo and EAS.
What’s the usual approach for sharing Android test builds with contributors outside the Play Store?
Do people generally prefer APKs, AABs, or Expo-hosted artifacts?
Interested in hearing what works well in open-source projects.
https://redd.it/1ptk6uu
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Github in decline?
I have seen recently a decent amount of projects switching to Codeberg from Github. Is it worth moving your OSS libraries over to Codeberg? Since Microsoft has taken over Github it just seems a little less then it once was sort of speak... Is Codeberg the next big thing for OSS?
I currently am still on Github but I am seriously considering at least mirroring my repos on Codeberg. Github continues to come out with not so great announcements and pricing changes. Codeberg remains free from what I can tell.
Any thoughts or insights on this topic?
https://redd.it/1ptnf7n
@r_opensource
I have seen recently a decent amount of projects switching to Codeberg from Github. Is it worth moving your OSS libraries over to Codeberg? Since Microsoft has taken over Github it just seems a little less then it once was sort of speak... Is Codeberg the next big thing for OSS?
I currently am still on Github but I am seriously considering at least mirroring my repos on Codeberg. Github continues to come out with not so great announcements and pricing changes. Codeberg remains free from what I can tell.
Any thoughts or insights on this topic?
https://redd.it/1ptnf7n
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
I built a small tool to save YouTube language content as MP3 for offline listening
Hi open source lovers!
I made a small open-source command-line noscript that lets you download YouTube videos or full playlists and save them as MP3 audio or MP4 in the highest available quality.
I originally built it for my own language learning. I often download podcasts, interviews, and lessons in my target language so I can listen offline, replay difficult sections, or do repeated listening and shadowing without relying on an internet connection.
It works without logging in, has no ads, and supports multiple downloads at once. You just run the noscript and follow the usage instructions in the README.
GitHub:
https://github.com/pH-7/Download-Simply-Videos-From-YouTube?tab=readme-ov-file#-download-any-videos-from-youtube
Sharing it here in case it’s useful to others. Feedback or ideas to make it more helpful for language learners are very welcome!
https://redd.it/1ptnq2f
@r_opensource
Hi open source lovers!
I made a small open-source command-line noscript that lets you download YouTube videos or full playlists and save them as MP3 audio or MP4 in the highest available quality.
I originally built it for my own language learning. I often download podcasts, interviews, and lessons in my target language so I can listen offline, replay difficult sections, or do repeated listening and shadowing without relying on an internet connection.
It works without logging in, has no ads, and supports multiple downloads at once. You just run the noscript and follow the usage instructions in the README.
GitHub:
https://github.com/pH-7/Download-Simply-Videos-From-YouTube?tab=readme-ov-file#-download-any-videos-from-youtube
Sharing it here in case it’s useful to others. Feedback or ideas to make it more helpful for language learners are very welcome!
https://redd.it/1ptnq2f
@r_opensource
GitHub
GitHub - pH-7/Download-Simply-Videos-From-YouTube: Python noscript that downloads and saves any of your favorite YouTube videos and…
Python noscript that downloads and saves any of your favorite YouTube videos and playlists. All you need to do is just run the Python noscript and follow the terminal prompt. - pH-7/Download-Simply-Vid...
I created a flutter app for IPTV play
so I saw iptv-org maintains a list of IPTV channels but doesn't have a player we need VLC to play. it kind of hacky way and not nice UX.
so i made a flutter app which will list it with logos ,quality,category, searching and nice UI UX.
i personally use it, and I have it on my github free to download all codes are opensource.
can be used on mobile , android TVs , laptop it's cross platform.
i don't own or claim anything other than the ui and flutter codes.
https://github.com/KTBsomen/freetv
https://redd.it/1ptq9ph
@r_opensource
so I saw iptv-org maintains a list of IPTV channels but doesn't have a player we need VLC to play. it kind of hacky way and not nice UX.
so i made a flutter app which will list it with logos ,quality,category, searching and nice UI UX.
i personally use it, and I have it on my github free to download all codes are opensource.
can be used on mobile , android TVs , laptop it's cross platform.
i don't own or claim anything other than the ui and flutter codes.
https://github.com/KTBsomen/freetv
https://redd.it/1ptq9ph
@r_opensource
GitHub
GitHub - KTBsomen/freetv
Contribute to KTBsomen/freetv development by creating an account on GitHub.
Any Android RTSP app you know about?
There are many on playstore but i want open source alternaitve.
Mobile camera -> RTSP -> View live feed in vlc
https://redd.it/1ptq2ca
@r_opensource
There are many on playstore but i want open source alternaitve.
Mobile camera -> RTSP -> View live feed in vlc
https://redd.it/1ptq2ca
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Which slack alternatives do you actually use and enjoy?
My team is looking for a straightforward solution for chatting, sharing files, and the occasional call but slack has become too cluttered and expensive for our needs
https://redd.it/1pts1cg
@r_opensource
My team is looking for a straightforward solution for chatting, sharing files, and the occasional call but slack has become too cluttered and expensive for our needs
https://redd.it/1pts1cg
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
khaos – simulating Kafka traffic and failure scenarios via CLI
# What My Project Does
khaos is a CLI tool for generating Kafka traffic from a YAML configuration.
It can spin up a local multi-broker Kafka cluster and simulate Kafka-level scenarios such as consumer lag buildup, hot partitions (skewed keys), rebalances, broker failures, and backpressure.
The tool can also generate structured JSON messages using Faker and publish them to Kafka topics.
It can run both against a local cluster and external Kafka clusters (including SASL / SSL setups).
# Target Audience
khaos is intended for developers and engineers working with Kafka who want a single tool to generate traffic and observe Kafka behavior.
Typical use cases include:
local testing
experimentation and learning
chaos and behavior testing
debugging Kafka consumers and producers
# Comparison
There are no widely adopted, feature-complete open-source tools focused specifically on simulating Kafka traffic and behavior.
In practice, most teams end up writing ad-hoc producer and consumer noscripts to reproduce Kafka scenarios.
khaos provides a reusable, configuration-driven CLI as an alternative to that approach.
Project Link:
https://github.com/aleksandarskrbic/khaos
(https://www.reddit.com/submit/?sourceid=t31ptr126)
https://redd.it/1ptsupg
@r_opensource
# What My Project Does
khaos is a CLI tool for generating Kafka traffic from a YAML configuration.
It can spin up a local multi-broker Kafka cluster and simulate Kafka-level scenarios such as consumer lag buildup, hot partitions (skewed keys), rebalances, broker failures, and backpressure.
The tool can also generate structured JSON messages using Faker and publish them to Kafka topics.
It can run both against a local cluster and external Kafka clusters (including SASL / SSL setups).
# Target Audience
khaos is intended for developers and engineers working with Kafka who want a single tool to generate traffic and observe Kafka behavior.
Typical use cases include:
local testing
experimentation and learning
chaos and behavior testing
debugging Kafka consumers and producers
# Comparison
There are no widely adopted, feature-complete open-source tools focused specifically on simulating Kafka traffic and behavior.
In practice, most teams end up writing ad-hoc producer and consumer noscripts to reproduce Kafka scenarios.
khaos provides a reusable, configuration-driven CLI as an alternative to that approach.
Project Link:
https://github.com/aleksandarskrbic/khaos
(https://www.reddit.com/submit/?sourceid=t31ptr126)
https://redd.it/1ptsupg
@r_opensource
GitHub
GitHub - aleksandarskrbic/khaos: Kafka data generator and load testing tool - generate fake messages, simulate producers and consumers…
Kafka data generator and load testing tool - generate fake messages, simulate producers and consumers, test broker failures, and run chaos engineering scenarios - GitHub - aleksandarskrbic/khaos:...
Repath Studio: Web-Based Vector Graphics Editor
https://github.com/repath-studio/repath-studio
https://redd.it/1ptufpl
@r_opensource
https://github.com/repath-studio/repath-studio
https://redd.it/1ptufpl
@r_opensource
GitHub
GitHub - repath-studio/repath-studio: A local web-based vector graphics editor that combines procedural tooling with traditional…
A local web-based vector graphics editor that combines procedural tooling with traditional design workflows. - GitHub - repath-studio/repath-studio: A local web-based vector graphics editor that c...
Open source mini-os project :)
https://github.com/pocofan1264/WayOS-Beta-
https://redd.it/1ptw6gg
@r_opensource
https://github.com/pocofan1264/WayOS-Beta-
https://redd.it/1ptw6gg
@r_opensource
GitHub
GitHub - pocofan1264/WayOS-Beta-: Shitty mini-OS made by 2 teenagers in python and A LOT of free time. Hope u enjoy :)
Shitty mini-OS made by 2 teenagers in python and A LOT of free time. Hope u enjoy :) - GitHub - pocofan1264/WayOS-Beta-: Shitty mini-OS made by 2 teenagers in python and A LOT of free time. Hope ...
Tpipe – Apple-style Audio Transparency for Linux (JACK / PipeWire)
open-source audio transparency tool for Unix-based systems built on the JACK audio engine. It provides real-time voice isolation and adaptive audio ducking, similar in concept to Apple’s Transparency mode
GitHub: https://github.com/beaterblank/tpipe
I’d appreciate feedback on the design and suggestions for improvement.
https://redd.it/1ptx9kb
@r_opensource
open-source audio transparency tool for Unix-based systems built on the JACK audio engine. It provides real-time voice isolation and adaptive audio ducking, similar in concept to Apple’s Transparency mode
GitHub: https://github.com/beaterblank/tpipe
I’d appreciate feedback on the design and suggestions for improvement.
https://redd.it/1ptx9kb
@r_opensource
GitHub
GitHub - beaterblank/tpipe: Audio Transparency tool for Unix-based systems that use JACK audio engine.
Audio Transparency tool for Unix-based systems that use JACK audio engine. - beaterblank/tpipe
LabFyre: Cus I got tired working around upstream limitations...
In short order, I was developing a few noscripts that would simulate sticky keys and Omacarhy's universal copy/paste, except it's on ctrl and not meta/super. I ran into a myriad of issues with this though, I'd end up with a feedback loop with universial copy/paste, thanks to dotool, and the sticky key implementation wasn't 1:1 with KDE, GNOME, or Windows. It had it's flaws and would actively affect gaming when I had it turned off due to how labwc does keybinds.
As a result I initially forked labwc to add keybind toggles, device blacklisting/whitelisting, and conditionals based on shell commands. I knew none of this would be merged into upstream, as they only want Labwc to understand wayland protocols and WL-roots protocols, no D-Bus,IPC, or anything else, probably including the flags I added to the binary to control it. So the features kind of spiraled from there into what I have LabFyre is currently.
As far as feature set compared to upstream, there's quite a bit.
multiple methods of turning on or off or limiting keybinds (by command flag, by device, and by the output of a shell command)
a noscript that fires upon reconfiguring the compositor
workspace control via command flag
a (WIP) tiling mode. (grid snapping mode works fine-ish, but smart resizing is experimental)
This still hold into the means of not being controllable via D-Bus or IPC, the only compositor control outside of wayland and WL-roots will be from command flags to the binary. So you could write plugins in any language. Bash, Zsh, Xonsh, python, java, zig... So long as it can run system commands, you can use it to control the compositor. Openbox themes are still supported as well as configs for upstream Labwc.
Note that the README isn't 100% deviod of Labwc links and mentions. I'm going to move all the documentation to the GitHub Wiki at some point, but the scdocs will still be maintained for offline reading. You'll need to compile it yourself and make a desktop file for your greeter, I am taking PRs for a PKGBUILD and hopefully someone can get it onto the AUR for me, as I can't figure out the needed keys to do it...
Obligatory link to the project: https://github.com/FyreX-opensource-design/labFyre/tree/master
https://redd.it/1ptvkow
@r_opensource
In short order, I was developing a few noscripts that would simulate sticky keys and Omacarhy's universal copy/paste, except it's on ctrl and not meta/super. I ran into a myriad of issues with this though, I'd end up with a feedback loop with universial copy/paste, thanks to dotool, and the sticky key implementation wasn't 1:1 with KDE, GNOME, or Windows. It had it's flaws and would actively affect gaming when I had it turned off due to how labwc does keybinds.
As a result I initially forked labwc to add keybind toggles, device blacklisting/whitelisting, and conditionals based on shell commands. I knew none of this would be merged into upstream, as they only want Labwc to understand wayland protocols and WL-roots protocols, no D-Bus,IPC, or anything else, probably including the flags I added to the binary to control it. So the features kind of spiraled from there into what I have LabFyre is currently.
As far as feature set compared to upstream, there's quite a bit.
multiple methods of turning on or off or limiting keybinds (by command flag, by device, and by the output of a shell command)
a noscript that fires upon reconfiguring the compositor
workspace control via command flag
a (WIP) tiling mode. (grid snapping mode works fine-ish, but smart resizing is experimental)
This still hold into the means of not being controllable via D-Bus or IPC, the only compositor control outside of wayland and WL-roots will be from command flags to the binary. So you could write plugins in any language. Bash, Zsh, Xonsh, python, java, zig... So long as it can run system commands, you can use it to control the compositor. Openbox themes are still supported as well as configs for upstream Labwc.
Note that the README isn't 100% deviod of Labwc links and mentions. I'm going to move all the documentation to the GitHub Wiki at some point, but the scdocs will still be maintained for offline reading. You'll need to compile it yourself and make a desktop file for your greeter, I am taking PRs for a PKGBUILD and hopefully someone can get it onto the AUR for me, as I can't figure out the needed keys to do it...
Obligatory link to the project: https://github.com/FyreX-opensource-design/labFyre/tree/master
https://redd.it/1ptvkow
@r_opensource
GitHub
GitHub - FyreX-opensource-design/labFyre: A Wayland window-stacking and tiling compositor that doesn't sacrifice modularity
A Wayland window-stacking and tiling compositor that doesn't sacrifice modularity - FyreX-opensource-design/labFyre
tchat-cli: prefill your AI chat app from the terminal with prompts and files!
https://github.com/varo6/tchat-cli
https://redd.it/1pu0ja4
@r_opensource
https://github.com/varo6/tchat-cli
https://redd.it/1pu0ja4
@r_opensource
GitHub
GitHub - varo6/tchat-cli
Contribute to varo6/tchat-cli development by creating an account on GitHub.
Looking for feedback and contributors on an open-source React Native + Expo mobile app
Hi everyone,
I’m working on an open-source mobile app built with React Native + Expo, and I’m trying to do the development as openly and transparently as possible.
At this stage, I’m not looking to promote a “finished product”, but rather to get help improving the project itself. I would really appreciate feedback or contributions in areas like:
\- Project structure and architecture
\- README and developer onboarding
\- Documentation quality
\- Performance and rendering patterns
\- Internationalization (currently switching between Georgian and Russian)
\- General React Native / Expo best practices
The repository is open-source and still evolving, and I’m very open to criticism, suggestions, and refactors. If you enjoy reviewing code, improving docs, or helping shape early-stage OSS projects, I’d love your input.
Repository:
https://github.com/georgetoloraia/selflink-mobile
If this isn’t the right place or flair for this kind of post, feel free to let me know and I’ll adjust. Thanks for your time.
https://redd.it/1ptzyq6
@r_opensource
Hi everyone,
I’m working on an open-source mobile app built with React Native + Expo, and I’m trying to do the development as openly and transparently as possible.
At this stage, I’m not looking to promote a “finished product”, but rather to get help improving the project itself. I would really appreciate feedback or contributions in areas like:
\- Project structure and architecture
\- README and developer onboarding
\- Documentation quality
\- Performance and rendering patterns
\- Internationalization (currently switching between Georgian and Russian)
\- General React Native / Expo best practices
The repository is open-source and still evolving, and I’m very open to criticism, suggestions, and refactors. If you enjoy reviewing code, improving docs, or helping shape early-stage OSS projects, I’d love your input.
Repository:
https://github.com/georgetoloraia/selflink-mobile
If this isn’t the right place or flair for this kind of post, feel free to let me know and I’ll adjust. Thanks for your time.
https://redd.it/1ptzyq6
@r_opensource
GitHub
GitHub - georgetoloraia/selflink-mobile: you can see swagger
you can see swagger. Contribute to georgetoloraia/selflink-mobile development by creating an account on GitHub.