|
14193
|
Peak by @taimesadi | Stardance
|
taimesadi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Peak by @taimesadi | Stardance
|
1793368492.0170555
|
1793973292.0170555
|
|
9013
|
My awesome macropad! by @tailschen6666 | Stardance
|
tailschen6666
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tailschen6666 | St Title: My awesome macropad! by @tailschen6666 | Stardance...
|
1793224472.5361404
|
1793829272.5361404
|
|
9021
|
My first slack bot! by @tailschen6666 | Stardance
|
tailschen6666
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @tailschen6666 | Sta Title: My first slack bot! by @tailschen6666 | Stardance...
|
1793321807.633438
|
1793926607.633438
|
|
25542
|
tibou by @taiebjemal | Stardance
|
taiebjemal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: tibou by @taiebjemal | Stardance
|
1793177591.3585477
|
1793782391.3585477
|
|
8233
|
Untitled project by @tahx09 | Stardance
|
tahx09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @tahx09 | Stardance
|
1793199065.6418958
|
1793803865.6418958
|
|
52606
|
Frictionless by @tahsinraiyan330 | Stardance
|
tahsinraiyan330
|
0
|
0.3
|
0
|
[]
|
[{"post_id": 52484, "ts": "202 [{"post_id": 52484, "ts": "2026-08-22T16:58:37Z", "hours": 0.3003, "text": "AuraMatch - Decode Their Signals & Confess with Confidence Are they into you, or just being polite? Run doubt checks, analyze psychological attraction signs, or write the ultimate confession letter."}]...
|
Title: Frictionless by @tahsinraiyan330 | Stardanc Title: Frictionless by @tahsinraiyan330 | Stardance
Devlogs:
AuraMatch - Decode Their Signals & Confess with Confidence Are they into you, or just being polite? Run doubt checks, analyze psychological attraction signs, or write the ultimate confession letter....
|
1793447709.224481
|
1794052509.224481
|
|
59366
|
oggy000 by @tahsinraiyan330 | Stardance
|
tahsinraiyan330
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-07T12:11:51Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Actually, I can not build the full slack bot. I can not un it for 24/7", "repo": "https://github.com/tahsinraiyan330/newwsss", "demo": "https://app.slack.com/client/E09V59WQY1E/C0P5NE354?_gl=1*rrz3ch*_gcl_au*MTUwODY5NzUyMi4xNzg3MzYyODI5"}]...
|
[{"post_id": 63503, "ts": "202 [{"post_id": 63503, "ts": "2026-09-07T12:07:35Z", "hours": 0.6742, "text": "I have built the slack bot but can not run it for 24/7"}]...
|
Title: oggy000 by @tahsinraiyan330 | Stardance
De Title: oggy000 by @tahsinraiyan330 | Stardance
Devlogs:
I have built the slack bot but can not run it for 24/7
Ships:
Actually, I can not build the full slack bot. I can not un it for 24/7...
|
1793641730.037167
|
1793728130.037167
|
|
46255
|
Rescue Rover by @tahsinisgone07 | Stardance
|
tahsinisgone07
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rescue Rover by @tahsinisgone07 | Stardance
|
1793378973.4334826
|
1793983773.4334826
|
|
72765
|
My awesome macropad! by @tahmidturjo195 | Stardanc My awesome macropad! by @tahmidturjo195 | Stardance...
|
tahmidturjo195
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tahmidturjo195 | S Title: My awesome macropad! by @tahmidturjo195 | Stardance...
|
1793641635.0086513
|
1794246435.0086513
|
|
31936
|
Humanoid robot by @tahmidkarim | Stardance
|
tahmidkarim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Humanoid robot by @tahmidkarim | Stardance
|
1793451288.1792629
|
1794056088.1792629
|
|
67647
|
AI Messenger by @tahmidhasnain666 | Stardance
|
tahmidhasnain666
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Messenger by @tahmidhasnain666 | Stardan Title: AI Messenger by @tahmidhasnain666 | Stardance...
|
1793732357.9797843
|
1794337157.9797843
|
|
47615
|
My awesome macropad! by @tahiel_bar | Stardance
|
tahiel_bar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tahiel_bar | Stard Title: My awesome macropad! by @tahiel_bar | Stardance...
|
1793188446.4127765
|
1793793246.4127765
|
|
47617
|
Modo IA by @tahiel_bar | Stardance
|
tahiel_bar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Modo IA by @tahiel_bar | Stardance
|
1793188448.1969166
|
1793793248.1969166
|
|
67583
|
Nosabo by @tahiel_bar | Stardance
|
tahiel_bar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Nosabo by @tahiel_bar | Stardance
|
1793732282.5455785
|
1794337082.5455785
|
|
60246
|
My own site! by @taherhatimali | Stardance
|
taherhatimali
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @taherhatimali | Stardance
|
1793641796.8086755
|
1794246596.8086755
|
|
60261
|
TAHOS by @taherhatimali | Stardance
|
taherhatimali
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: TAHOS by @taherhatimali | Stardance
|
1793641807.893032
|
1794246607.893032
|
|
29198
|
My own site! by @tahamkhan78 | Stardance
|
tahamkhan78
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @tahamkhan78 | Stardance
|
1793559321.7773435
|
1794164121.7773435
|
|
48764
|
My awesome macropad! by @tahaislam22 | Stardance
|
tahaislam22
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tahaislam22 | Star Title: My awesome macropad! by @tahaislam22 | Stardance...
|
1793245745.1651614
|
1793850545.1651614
|
|
55498
|
My very own WebOS by @tahaijaz | Stardance
|
tahaijaz
|
0
|
1.12
|
0
|
[]
|
[{"post_id": 57322, "ts": "202 [{"post_id": 57322, "ts": "2026-08-29T13:16:01Z", "hours": 1.1244, "text": "Might be because I use windows that I always got amazed by MacOS. The cleanliness of the OS really hides the restriction apple imposes to keep you into their environment. So I started building TIos, a webOS parody of MacOS. Its still in a very rough form but with the help of AI, I think I will get there."}]...
|
Title: My very own WebOS by @tahaijaz | Stardance
Title: My very own WebOS by @tahaijaz | Stardance
Devlogs:
Might be because I use windows that I always got amazed by MacOS. The cleanliness of the OS really hides the restriction apple imposes to keep you into their environment. So I started building TIos, a webOS parody of MacOS. Its still in a very rough form but with the help of AI, I think I will get there....
|
1793163138.7142763
|
1793767938.7142763
|
|
22575
|
FreelanceScore by @tahafaisal | Stardance
|
tahafaisal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FreelanceScore by @tahafaisal | Stardance
|
1792932816.6177163
|
1793796816.6177163
|
|
44581
|
Personal Website by @tahafaisal | Stardance
|
tahafaisal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Personal Website by @tahafaisal | Stardance
|
1792921794.1928332
|
1793785794.1928332
|
|
47572
|
Vibely by @tahafaisal | Stardance
|
tahafaisal
|
0
|
0.38
|
0
|
[]
|
[{"post_id": 46563, "ts": "202 [{"post_id": 46563, "ts": "2026-08-13T21:44:08Z", "hours": 0.3792, "text": "Just started with the project initialization I choose the best tech stack for my requirements and created the folder and essentials files tree I am terrible with backend so ill let cline cook it for me till then I am designing the logo for my app"}]...
|
Title: Vibely by @tahafaisal | Stardance
Devlogs: Title: Vibely by @tahafaisal | Stardance
Devlogs:
Just started with the project initialization I choose the best tech stack for my requirements and created the folder and essentials files tree I am terrible with backend so ill let cline cook it for me till then I am designing the logo for my app...
|
1793188174.0896418
|
1793792974.0896418
|
|
62239
|
Pitchly by @tahafaisal | Stardance
|
tahafaisal
|
0
|
1.95
|
0
|
[]
|
[{"post_id": 68795, "ts": "202 [{"post_id": 68795, "ts": "2026-09-15T19:23:08Z", "hours": 1.9464, "text": "mvp is ready"}]...
|
Title: Pitchly by @tahafaisal | Stardance
Devlogs Title: Pitchly by @tahafaisal | Stardance
Devlogs:
mvp is ready...
|
1793652933.2428725
|
1794257733.2428725
|
|
42744
|
My awesome macropad! by @tahaelyare | Stardance
|
tahaelyare
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tahaelyare | Stard Title: My awesome macropad! by @tahaelyare | Stardance...
|
1793188205.017017
|
1793793005.017017
|
|
33266
|
Frictionless by @tahach | Stardance
|
tahach
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @tahach | Stardance
|
1793332071.249984
|
1793936871.249984
|
|
60299
|
My first slack bot! by @tahaamir | Stardance
|
tahaamir
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @tahaamir | Stardanc Title: My first slack bot! by @tahaamir | Stardance...
|
1793641842.4953594
|
1794246642.4953594
|
|
72400
|
Untitled project by @taha_tagh | Stardance
|
taha_tagh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @taha_tagh | Stardance
|
1793461643.8921206
|
1794066443.8921206
|
|
30450
|
My awesome macropad! by @taha_solouki_2 | Stardanc My awesome macropad! by @taha_solouki_2 | Stardance...
|
taha_solouki_2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @taha_solouki_2 | S Title: My awesome macropad! by @taha_solouki_2 | Stardance...
|
1793393480.6229348
|
1793998280.6229348
|
|
39106
|
My own site! by @taha_solouki_2 | Stardance
|
taha_solouki_2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @taha_solouki_2 | Stardance
|
1793210081.8434322
|
1793814881.8434322
|
|
33889
|
Frictionless by @taha_justanieah | Stardance
|
taha_justanieah
|
0
|
0.75
|
0
|
[]
|
[{"post_id": 27266, "ts": "202 [{"post_id": 27266, "ts": "2026-07-12T18:02:20Z", "hours": 0.7453, "text": "Devlog #1 Fixing Formatting Issues"}]...
|
Title: Frictionless by @taha_justanieah | Stardanc Title: Frictionless by @taha_justanieah | Stardance
Devlogs:
Devlog #1 Fixing Formatting Issues...
|
1793339818.3610015
|
1793944618.3610015
|
|
71546
|
My first slack bot! by @taha489225 | Stardance
|
taha489225
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @taha489225 | Starda Title: My first slack bot! by @taha489225 | Stardance...
|
1793681242.6391144
|
1794286042.6391144
|
|
47446
|
knowledge by @tagabergenova | Stardance
|
tagabergenova
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: knowledge by @tagabergenova | Stardance
|
1793181178.3195255
|
1793785978.3195255
|
|
63300
|
My awesome macropad! by @tafsinn | Stardance
|
tafsinn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tafsinn | Stardanc Title: My awesome macropad! by @tafsinn | Stardance...
|
1793660123.005856
|
1794264923.005856
|
|
63305
|
me by @tafsinn | Stardance
|
tafsinn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: me by @tafsinn | Stardance
|
1793660128.8817475
|
1794264928.8817475
|
|
63317
|
Stellar OS by @tafsinn | Stardance
|
tafsinn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Stellar OS by @tafsinn | Stardance
|
1793660142.2953844
|
1794264942.2953844
|
|
13565
|
My very own WebOS by @tafata | Stardance
|
tafata
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @tafata | Stardance
|
1793458343.5624502
|
1794063143.5624502
|
|
16135
|
Frictionless by @taepioca | Stardance
|
taepioca
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @taepioca | Stardance
|
1793173818.0500777
|
1793778618.0500777
|
|
23462
|
Rod by @tadeas_ditte | Stardance
|
tadeas_ditte
|
0
|
3.36
|
0
|
[]
|
[{"post_id": 15344, "ts": "202 [{"post_id": 15344, "ts": "2026-06-24T22:57:36Z", "hours": 0.9131, "text": "Played around with sso via google, github and discord, I only managed to implement github for now because google cloud is not very intuitive and discord is a feature i am not sure i want to use [the plan was that someone who sso’d via dc would have a dc connection in their profile so you could actually contact them to merge trees or whatever…] and ci pipelines"}, {"post_id": 13446, "ts": "2026-06-22T00:49:41Z", "hours": 1.4228, "text": "Added a minimalistic dashboard, fixed ci pipeline and started working on oauth via google, discord and gh. Also updated composer and pnpm, and added README"}, {"post_id": 13047, "ts": "2026-06-21T10:27:45Z", "hours": 1.0222, "text": "I have written a database schema that could possibly work for my project, and i have thought about possible features that could be useful to add now"}]...
|
Title: Rod by @tadeas_ditte | Stardance
Devlogs:
Title: Rod by @tadeas_ditte | Stardance
Devlogs:
I have written a database schema that could possibly work for my project, and i have thought about possible features that could be useful to add now
Added a minimalistic dashboard, fixed ci pipeline and started working on oauth via google, discord and gh. Also updated composer and pnpm, and added README
Played around with sso via google, github and discord, I only managed to implement github for now because google cloud is not very intuitive and discord is a feature i am not sure i want to use [the plan was that someone who sso’d via dc would have a dc connection in their profile so you could actually contact them to merge trees or whatever…] and ci pipelines...
|
1793562955.2595005
|
1794167755.2595005
|
|
40155
|
CTFp by @tadeas_ditte | Stardance
|
tadeas_ditte
|
0
|
15.99
|
0
|
[]
|
[{"post_id": 35199, "ts": "202 [{"post_id": 35199, "ts": "2026-07-26T13:53:39Z", "hours": 15.9936, "text": "CTFp — Devlog #1CTFp is a self-hosted CTF (Capture The Flag) competition platform I’m building from scratch. Backend is Laravel 13 (PHP 8.3), frontend is Vue 3 + TypeScript with Tailwind and shadcn-vue components, everything running in Docker for dev. Started the repo on July 16. First few days were mostly scaffolding, got the Laravel + Vue split running together in Docker with hot reload on both sides (PHP/Blade changes need nothing, Vite handles the frontend), wrote a small qol script to spin the dev environment up, and set up CI with ESLint/Prettier. From there I built out auth, login and register pages on the frontend, an auth controller on the backend using Sanctum, and added Authentik as an OAuth provider so the platform can hook into an existing identity provider instead of only rolling its own accounts. Alongside that I added Gravatar support with a fallback to generated initials for users without one. Usernames needed some care for a public platform, so I pulled in a blocklist (based on LDNOOBW) with validation, and set up a workflow to keep it synced from upstream.On the data model side: users, orgs, and invites all have migrations and factories now, laying the groundwork for team-based competitions rather than just solo accounts. Most recently I’ve been on the frontend shell, landing page, branding, a sidebar for the user area, and pulling in shadcn UI blocks to speed up building out the rest of the interface. Still early. Core auth and org/invite data model are in place. Next is actually building out CTF-specific functionality (challenges, scoring, competitions) on top of this foundation. Also i am too lazy to spin the docker containers rn so here is a git tree instead :3"}]...
|
Title: CTFp by @tadeas_ditte | Stardance
Devlogs: Title: CTFp by @tadeas_ditte | Stardance
Devlogs:
CTFp — Devlog #1CTFp is a self-hosted CTF (Capture The Flag) competition platform I’m building from scratch. Backend is Laravel 13 (PHP 8.3), frontend is Vue 3 + TypeScript with Tailwind and shadcn-vue components, everything running in Docker for dev. Started the repo on July 16. First few days were mostly scaffolding, got the Laravel + Vue split running together in Docker with hot reload on both sides (PHP/Blade changes need nothing, Vite handles the frontend), wrote a small qol script to spin the dev environment up, and set up CI with ESLint/Prettier. From there I built out auth, login and register pages on the frontend, an auth controller on the backend using Sanctum, and added Authentik as an OAuth provider so the platform can hook into an existing identity provider instead of only rolling its own accounts. Alongside that I added Gravatar support with a fallback to generated initials for users without one. Usernames needed some care for a public platform, so I pulled in a blocklist (based on LDNOOBW) with validation, and set up a workflow to keep it synced from upstream.On the data model side: users, orgs, and invites all have migrations and factories now, laying the groundwork for team-based competitions rather than just solo accounts. Most recently I’ve been on the frontend shell, landing page, branding, a sidebar for the user area, and pulling in shadcn UI blocks to speed up building out the rest of the interface. Still early. Core auth and org/invite data model are in place. Next is actually building out CTF-specific functionality (challenges, scoring, competitions) on top of this foundation. Also i am too lazy to spin the docker containers rn so here is a git tree instead :3...
|
1793458513.9006133
|
1794063313.9006133
|
|
40158
|
Caduceus by @tadeas_ditte | Stardance
|
tadeas_ditte
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Caduceus by @tadeas_ditte | Stardance
|
1793501520.8307009
|
1794106320.8307009
|
|
40504
|
Rozhanitsy by @tadeas_ditte | Stardance
|
tadeas_ditte
|
1
|
11.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-03T02:37:27Z", "hours": 11.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a website where you can generate API keys to talk to a parsed version of nvd db that is matched with vendors [eg. wordpress], and products [eg. pluginxyz], so you can ask is wordpress:pluginxyz v6.9 vulnerable? if yes, it spits CVE, severity and the whole bunch. Official cli implementation will be in another repo under my account for the client [scanee?] side", "repo": "https://github.com/TadeasDitte/Rozhanitsy", "demo": "https://rozhanitsy.tadesrv.eu"}]...
|
[{"post_id": 39827, "ts": "202 [{"post_id": 39827, "ts": "2026-08-03T02:34:09Z", "hours": 0.6861, "text": "Rozhanitsy Devlog 3 And this version comes to an end So, i just added some features to get extra space to write this devlog, amongst these are: Gravatar check cuz why not Authentik sso because it is something i would have wanted Anyway, time to explain the naming just in case anyone is wondering, Rozhanitsy are the slavic equivallent of Morai, a.k.a the faiths and Svetovit is the god of war so like, rozhanitsy see it happen, svetovit detects and then helps us end it. Kinda a fun little meaning. Anyway, the thing is now in production ready state and i am working on svetovit, hopefully it will be slightly less vibecoded in the v1 phase but meh, i will redo it anyways when i will have more time. The plan is to support detection for wp, drupal and joomla + plugins. Also, i never mentioned it on here i think but the entire meaning of this project was to detect tenants on shared servers that don’t maintain their stuff and get us crypto miners lolsies Anyway, thanks for reading, imma ship now"}, {"post_id": 39795, "ts": "2026-08-03T00:27:27Z", "hours": 6.7772, "text": "Rozhanitsy Devlog 2 Vuln intel service — feed it installed software, get back which CVEs actually apply to it. 27 commits, empty lockfile to a dockerized app with a working sync pipeline and admin panel.Started with the schema: CpeMap, Product, Vendor, Vulnerability, VulnerabilityRange, ScanHost, Source, SyncState. That’s basically the whole app in one commit — vendors/products are a catalog I curate, CVEs link to them through ranges, hosts get matched against those ranges via CPE strings. Seeded sources instead of hardcoding “nvd” everywhere, since I figured I’d want other feeds eventually.Added scan_logs and unmatched_lookups, folded the 2FA columns migration into the users table migration instead of leaving it bolted on separately. Wrote VersionComparator, gave NVD explicit precedence over whatever else might get added later.Pulled in Sanctum, cleaned out migration cruft, updated models to match.Core loop went in next: SyncNvdVulnerabilities command, VulnCheckController, rate limiting, POST /api/vulns/check. CPE lookup → range join → version comparison → vulnerable list, with unmatched stuff parked in its own table so I can go add it to the catalog later instead of it just vanishing. Wrote a pile of tests right after — factories for everything, sync tests, vuln check tests, CPE resolver tests, rate limit tests.Small cleanup pass: slugs in the seeder, more test coverage. Then went back and tore hardcoded NVD assumptions out of the sync command and controller — added a migration so sources can carry their own driver config instead of assuming NVD forever. Wanted that fixed before the app grew around the assumption.Docker next — Dockerfile, compose, entrypoint, opcache config, a CreateScanHost command for provisioning from the CLI. Then the whole frontend in one go: dashboard, a tokens page so scan hosts can self-serve Sanctum tokens, admin dashboard, admin user management, GrantAdmin command, rewrote Welcome (cut it by more than half, mostly bloat). Wired up HandleInertiaRequests so props actually reach the frontend.Wrote the wiki same day as the features it documents — API reference, CLI reference, deployment, schema, operations. Doing it same-day beats doing it a month later once I’ve forgotten why something works the way it does.Found and fixed a memory leak in the sync command — only showed up once I ran it against the real NVD feed instead of test fixtures. Built out actual vendor/product matching: RelinkVulnerabilityRanges command, an admin products page for curating the catalog through the UI, vendor/product seeders with a real starter set.Then a commit I titled, honestly, “deshittified plugin detection.” Pulled the matching logic out of the sync command into its own VulnerabilityRangeBuilder, added an OR-group clause to vulnerability_ranges so one CVE can express “affects 1.2–1.5 OR 2.0–2.3” without hacks, added RebuildVulnerabilityRanges to regenerate ranges without re-hitting NVD. Every project has one of these commits where you fix the thing you hated three days ago.Simplified SECURITY.md, moved the wiki over to GitHub’s wiki and trimmed the in-repo copies to a README with links, merged, added CI and dependabot. Then put the full wiki files back in the repo right after — GitHub wikis are a separate repo under the hood and they drift, didn’t want to rely on it alone.Last commit: made the vuln-check API return a confidence level when it can’t pin down a version instead of silently guessing. Better to say “not sure, but here’s our best guess” than fake precision.Net result: NVD ingest → CPE resolution → version ranges → match API, admin UI to curate the catalog, dockerized, test coverage across the sync command, comparator, API, rate limits, and admin auth."}, {"post_id": 36381, "ts": "2026-07-28T13:38:35Z", "hours": 3.4539, "text": "Rozhanisty devlog #1: laying the foundation Started Rozhanisty today — a tool that pulls vulnerability data from the NIST NVD API and lets a CLI scanner check local software for known CVEs against installed versions. Spent most of today on the database schema instead of anything flashy, but this is the part that has to be right before anything else works: vendors / products — normalized so a vendor (e.g. wordpress ) can have multiple products ( core , plugin , theme , etc.), since NVD data is a mess of vendor/product pairs that need de-duping. cpe_maps — maps NVD’s CPE vendor/product strings to my normalized vendor/product, with exact vs fuzzy match types since NVD naming is inconsistent and I’ll need fuzzy matching for products that don’t map 1:1. vulnerabilities — the actual CVE records: CVSS score/vector/version, description, published/modified dates, and the raw CPE config as JSON so I don’t lose data while I figure out matching logic. vulnerability_ranges — the important one. Each CVE can affect multiple version ranges per component, so this breaks it out with version_start / version_end (inclusive flags included, because NVD ranges are sometimes open-ended) and a match_confidence enum so the scanner can flag “we’re not 100% sure this applies to you.” Stack is Laravel on the backend (queues will probably handle the NVD pulls later) with Vue for whatever dashboard/UI ends up existing for making API keys. Next up: writing the ingestion job that actually pulls from the NVD API and populates these tables."}]...
|
Title: Rozhanitsy by @tadeas_ditte | Stardance
De Title: Rozhanitsy by @tadeas_ditte | Stardance
Devlogs:
Rozhanisty devlog #1: laying the foundation Started Rozhanisty today — a tool that pulls vulnerability data from the NIST NVD API and lets a CLI scanner check local software for known CVEs against installed versions. Spent most of today on the database schema instead of anything flashy, but this is the part that has to be right before anything else works: vendors / products — normalized so a vendor (e.g. wordpress ) can have multiple products ( core , plugin , theme , etc.), since NVD data is a mess of vendor/product pairs that need de-duping. cpe_maps — maps NVD’s CPE vendor/product strings to my normalized vendor/product, with exact vs fuzzy match types since NVD naming is inconsistent and I’ll need fuzzy matching for products that don’t map 1:1. vulnerabilities — the actual CVE records: CVSS score/vector/version, description, published/modified dates, and the raw CPE config as JSON so I don’t lose data while I figure out matching logic. vulnerability_ranges — the important one. Each CVE can affect multiple version ranges per component, so this breaks it out with version_start / version_end (inclusive flags included, because NVD ranges are sometimes open-ended) and a match_confidence enum so the scanner can flag “we’re not 100% sure this applies to you.” Stack is Laravel on the backend (queues will probably handle the NVD pulls later) with Vue for whatever dashboard/UI ends up existing for making API keys. Next up: writing the ingestion job that actually pulls from the NVD API and populates these tables.
Rozhanitsy Devlog 2 Vuln intel service — feed it installed software, get back which CVEs actually apply to it. 27 commits, empty lockfile to a dockerized app with a working sync pipeline and admin panel.Started with the schema: CpeMap, Product, Vendor, Vulnerability, VulnerabilityRange, ScanHost, Source, SyncState. That’s basically the whole app in one commit — vendors/products are a catalog I curate, CVEs link to them through ranges, hosts get matched against those ranges via CPE strings. Seeded sources instead of hardcoding “nvd” everywhere, since I figured I’d want other feeds eventually.Added scan_logs and unmatched_lookups, folded the 2FA columns migration into the users table migration instead of leaving it bolted on separately. Wrote VersionComparator, gave NVD explicit precedence over whatever else might get added later.Pulled in Sanctum, cleaned out migration cruft, updated models to match.Core loop went in next: SyncNvdVulnerabilities command, VulnCheckController, rate limiting, POST /api/vulns/check. CPE lookup → range join → version comparison → vulnerable list, with unmatched stuff parked in its own table so I can go add it to the catalog later instead of it just vanishing. Wrote a pile of tests right after — factories for everything, sync tests, vuln check tests, CPE resolver tests, rate limit tests.Small cleanup pass: slugs in the seeder, more test coverage. Then went back and tore hardcoded NVD assumptions out of the sync command and controller — added a migration so sources can carry their own driver config instead of assuming NVD forever. Wanted that fixed before the app grew around the assumption.Docker next — Dockerfile, compose, entrypoint, opcache config, a CreateScanHost command for provisioning from the CLI. Then the whole frontend in one go: dashboard, a tokens page so scan hosts can self-serve Sanctum tokens, admin dashboard, admin user management, GrantAdmin command, rewrote Welcome (cut it by more than half, mostly bloat). Wired up HandleInertiaRequests so props actually reach the frontend.Wrote the wiki same day as the features it documents — API reference, CLI reference, deployment, schema, operations. Doing it same-day beats doing it a month later once I’ve forgotten why something works the way it does.Found and fixed a memory leak in the sync command — only showed up once I ran it against the real NVD feed instead of test fixtures. Built out actual vendor/product matching: RelinkVulnerabilityRanges command, an admin products page for curating the catalog through the UI, vendor/product seeders with a real starter set.Then a commit I titled, honestly, “deshittified plugin detection.” Pulled the matching logic out of the sync command into its own VulnerabilityRangeBuilder, added an OR-group clause to vulnerability_ranges so one CVE can express “affects 1.2–1.5 OR 2.0–2.3” without hacks, added RebuildVulnerabilityRanges to regenerate ranges without re-hitting NVD. Every project has one of these commits where you fix the thing you hated three days ago.Simplified SECURITY.md, moved the wiki over to GitHub’s wiki and trimmed the in-repo copies to a README with links, merged, added CI and dependabot. Then put the full wiki files back in the repo right after — GitHub wikis are a separate repo under the hood and they drift, didn’t want to rely on it alone.Last commit: made the vuln-check API return a confidence level when it can’t pin down a version instead of silently guessing. Better to say “not sure, but here’s our best guess” than fake precision.Net result: NVD ingest → CPE resolution → version ranges → match API, admin UI to curate the catalog, dockerized, test coverage across the sync command, comparator, API, rate limits, and admin auth.
Rozhanitsy Devlog 3 And this version comes to an end So, i just added some features to get extra space to write this devlog, amongst these are: Gravatar check cuz why not Authentik sso because it is something i would have wanted Anyway, time to explain the naming just in case anyone is wondering, Rozhanitsy are the slavic equivallent of Morai, a.k.a the faiths and Svetovit is the god of war so like, rozhanitsy see it happen, svetovit detects and then helps us end it. Kinda a fun little meaning. Anyway, the thing is now in production ready state and i am working on svetovit, hopefully it will be slightly less vibecoded in the v1 phase but meh, i will redo it anyways when i will have more time. The plan is to support detection for wp, drupal and joomla + plugins. Also, i never mentioned it on here i think but the entire meaning of this project was to detect tenants on shared servers that don’t maintain their stuff and get us crypto miners lolsies Anyway, thanks for reading, imma ship now
Ships:
I made a website where you can generate API keys to talk to a parsed version of nvd db that is matched with vendors [eg. wordpress], and products [eg. pluginxyz], so you can ask is wordpress:pluginxyz v6.9 vulnerable? if yes, it spits CVE, severity and the whole bunch. Official cli implementation will be in another repo under my account for the client [scanee?] side...
|
1793667624.8856661
|
1793754024.8856661
|
|
40262
|
my APOD site by @tadeas-kucharik | Stardance
|
tadeas-kucharik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my APOD site by @tadeas-kucharik | Stardanc Title: my APOD site by @tadeas-kucharik | Stardance...
|
1793558983.5915067
|
1794163783.5915067
|
|
40268
|
Tadeas Website by @tadeas-kucharik | Stardance
|
tadeas-kucharik
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-27T18:40:20Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "🚀 Devlog Made great progress on Tadeas Digital Canvas today! I focused on improving the overall stability, refining existing features, and polishing the user experience. AI Usage: I used AI to help debug issues, improve some parts of the code, and refine text content. The website’s design, implementation, and overall development were done by me. What’s new: 🛠️ Fixed several bugs ✨ Improved the UI and overall usability ⚡ Enhanced performance and stability 🚧 Continued developing new features I’m excited to see the project coming together. There are still plenty of ideas to implement, and I’m looking forward to sharing more updates soon. Feel free to explore the project, try different features, and let me know if you find any bugs or have suggestions for improvements. Every bit of feedback is appreciated! 💙", "repo": "https://github.com/computerwin11pc-cmd/Website", "demo": "https://website-brown-one-41.vercel.app/"}]...
|
[{"post_id": 35688, "ts": "202 [{"post_id": 35688, "ts": "2026-07-27T09:00:34Z", "hours": 0.7961, "text": "🚀 Devlog #1 — Tadeas Digital CanvasAnother step forward in the development of the project! 🔥I’ve been working on improving the overall system, refining features, and making the user experience better with every update.✅ Bug fixes✅ Improved stability✅ Feature improvements✅ Preparing for future updatesThe project is slowly moving forward, and every update makes it better. 💻✨What’s coming next:🔹 New features🔹 Better design🔹 Performance improvements🔹 More improvements based on ideas and feedbackThank you to everyone who follows the development! 🚀#Devlog #Coding #WebDevelopment #BuildInPublic"}]...
|
Title: Tadeas Website by @tadeas-kucharik | Starda Title: Tadeas Website by @tadeas-kucharik | Stardance
Devlogs:
🚀 Devlog #1 — Tadeas Digital CanvasAnother step forward in the development of the project! 🔥I’ve been working on improving the overall system, refining features, and making the user experience better with every update.✅ Bug fixes✅ Improved stability✅ Feature improvements✅ Preparing for future updatesThe project is slowly moving forward, and every update makes it better. 💻✨What’s coming next:🔹 New features🔹 Better design🔹 Performance improvements🔹 More improvements based on ideas and feedbackThank you to everyone who follows the development! 🚀#Devlog #Coding #WebDevelopment #BuildInPublic
Ships:
🚀 Devlog Made great progress on Tadeas Digital Canvas today! I focused on improving the overall stability, refining existing features, and polishing the user experience. AI Usage: I used AI to help debug issues, improve some parts of the code, and refine text content. The website’s design, implementation, and overall development were done by me. What’s new: 🛠️ Fixed several bugs ✨ Improved the UI and overall usability ⚡ Enhanced performance and stability 🚧 Continued developing new features I’m excited to see the project coming together. There are still plenty of ideas to implement, and I’m looking forward to sharing more updates soon. Feel free to explore the project, try different features, and let me know if you find any bugs or have suggestions for improvements. Every bit of feedback is appreciated! 💙...
|
1793645554.5201707
|
1793731954.5201707
|
|
40996
|
Tadeas WebOs by @tadeas-kucharik | Stardance
|
tadeas-kucharik
|
0
|
0.38
|
0
|
[]
|
[{"post_id": 36619, "ts": "202 [{"post_id": 36619, "ts": "2026-07-28T20:56:25Z", "hours": 0.3839, "text": "🚀 Devlog #1 Started working on Tadeas WebOS. Added the first homepage design and improved the overall layout. More features coming soon."}]...
|
Title: Tadeas WebOs by @tadeas-kucharik | Stardanc Title: Tadeas WebOs by @tadeas-kucharik | Stardance
Devlogs:
🚀 Devlog #1 Started working on Tadeas WebOS. Added the first homepage design and improved the overall layout. More features coming soon....
|
1793533990.176508
|
1794138790.176508
|
|
9030
|
Truemask by @tada | Stardance
|
tada
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Truemask by @tada | Stardance
|
1793170451.9743483
|
1793775251.9743483
|
|
61220
|
Jazzy box by @taco_taim | Stardance
|
taco_taim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Jazzy box by @taco_taim | Stardance
|
1793648878.3932052
|
1794253678.3932052
|
|
61267
|
open cv thingy by @taco_taim | Stardance
|
taco_taim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: open cv thingy by @taco_taim | Stardance
|
1793648944.9295301
|
1794253744.9295301
|
|
61921
|
imposter by @taco_taim | Stardance
|
taco_taim
|
1
|
34.45
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-26T19:10:40Z", "hours": 34.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "imposter is a color reaction game made in python. every level has 3 elements rectangles or circles. one of the elements is in a different color, you need to pick your suspect with a time limit. i managed to make a script to read the level files. and a cool tutorial in pygame (its not easy) and I’m really proud of it :3 to play the game you will need to clone the repo ‘git clone https://github.com/thearmadiliking/imposter ’, install python and pygame. to run it run main.py. and don’t forget to give the repo a star :3", "repo": "https://github.com/thearmadiliking/imposter", "demo": "https://github.com/thearmadiliking/imposter/releases"}]...
|
[{"post_id": 75380, "ts": "202 [{"post_id": 75380, "ts": "2026-09-29T21:43:49Z", "hours": 0.4522, "text": "i added a release…."}, {"post_id": 74094, "ts": "2026-09-26T17:38:30Z", "hours": 8.9014, "text": "i did all of the polishing for the game and I’m ready to ship!!!"}, {"post_id": 73302, "ts": "2026-09-24T20:07:01Z", "hours": 1.6467, "text": "i finished the tutorial animation the only thing left for it is the voiceover."}, {"post_id": 73245, "ts": "2026-09-24T17:33:58Z", "hours": 2.9456, "text": "i started working on the totorial"}, {"post_id": 73075, "ts": "2026-09-24T10:12:05Z", "hours": 11.3025, "text": "i added a lvl picker and polished the overall game loop (and repairing the ship)"}, {"post_id": 70785, "ts": "2026-09-19T19:18:20Z", "hours": 1.2122, "text": "making a tui setup menu"}, {"post_id": 70736, "ts": "2026-09-19T17:49:10Z", "hours": 2.8361, "text": "i added the gameplay after you lode the level."}, {"post_id": 70610, "ts": "2026-09-19T13:30:40Z", "hours": 5.5264, "text": "i made a level reading test that takes a .lvl file and extracts the info and format it."}]...
|
Title: imposter by @taco_taim | Stardance
Devlogs Title: imposter by @taco_taim | Stardance
Devlogs:
i made a level reading test that takes a .lvl file and extracts the info and format it.
i added the gameplay after you lode the level.
making a tui setup menu
i added a lvl picker and polished the overall game loop (and repairing the ship)
i started working on the totorial
i finished the tutorial animation the only thing left for it is the voiceover.
i did all of the polishing for the game and I’m ready to ship!!!
i added a release….
Ships:
imposter is a color reaction game made in python. every level has 3 elements rectangles or circles. one of the elements is in a different color, you need to pick your suspect with a time limit. i managed to make a script to read the level files. and a cool tutorial in pygame (its not easy) and I’m really proud of it :3 to play the game you will need to clone the repo ‘git clone https://github.com/thearmadiliking/imposter ’, install python and pygame. to run it run main.py. and don’t forget to give the repo a star :3...
|
1793684981.7369318
|
1793771381.7369318
|
|
65685
|
player-pad by @taco_taim | Stardance
|
taco_taim
|
0
|
12.35
|
0
|
[]
|
[{"post_id": 77233, "ts": "202 [{"post_id": 77233, "ts": "2026-10-06T06:28:43Z", "hours": 0.65, "text": "i finished working on the case"}, {"post_id": 76525, "ts": "2026-10-03T20:24:14Z", "hours": 2.3669, "text": "i started working on the case :3"}, {"post_id": 75893, "ts": "2026-10-01T14:58:23Z", "hours": 4.2003, "text": "i made the routing and painted the pcb - routing i routed the pcb twice - painting i took a screenshot of the pcb and imported it to krita for painting"}, {"post_id": 73773, "ts": "2026-09-25T22:38:19Z", "hours": 5.1336, "text": "making a schematic i made a schematic for a 3x2 metrix a screen and a rfid reader"}]...
|
Title: player-pad by @taco_taim | Stardance
Devlo Title: player-pad by @taco_taim | Stardance
Devlogs:
making a schematic i made a schematic for a 3x2 metrix a screen and a rfid reader
i made the routing and painted the pcb - routing i routed the pcb twice - painting i took a screenshot of the pcb and imported it to krita for painting
i started working on the case :3
i finished working on the case...
|
1793703365.8059766
|
1794308165.8059766
|
|
68112
|
1:1 gear kit by @taco_taim | Stardance
|
taco_taim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 1:1 gear kit by @taco_taim | Stardance
|
1793116480.040045
|
1793721280.040045
|