GitHub - ovumcy/ovumcy-web: Self-hosted menstrual cycle tracker. Privacy-first, Docker-ready, beautiful. Track periods, predict cycles, own your health data.
github.com
Self-hosted menstrual cycle tracker. Privacy-first, Docker-ready, beautiful. Track periods, predict cycles, own your health data. - ovumcy/ovumcy-web

My wife needed a cycle tracker. Everything out there was either Flo (which got sued twice for sharing health data) or an abandoned GitHub project. So I built Ovumcy. Single Go binary, SQLite, Docker-ready. No analytics, no third-party APIs, no cloud. Your data stays on your server. Features: period tracking, symptom logging, predictions (ovulation, fertile window), statistics, CSV/JSON export, dark mode, Russian and English. Just pushed v0.2.5. Looking for feedback from real users.

  • Rimu@piefed.socialEnglish
    0·
    2 months ago

    I was going to recommend this to someone I know but when I realised your readme.md is entirely AI-generated, I guess the whole project is probably vibe-coded. I can’t in good conscience recommend someone trust their health data to a vide-coded app because they tend to have security problems.

    Also all ai-generated code is public domain so your AGPL license is kinda empty. Might as well use MIT.

    • terraincognita@lemmy.worldOPEnglish
      0·
      2 months ago

      I do use AI tools while developing this project, but I also have a BSc in Computer Science. AI is a productivity tool.

      Security is something I take seriously, especially since the project deals with health data. All code has test and you’re welcome to inspect the repository yourself or point out any specific security concerns if you notice them.

      Regarding licensing: the AGPL license applies to the project as a whole regardless of the tools used to write parts of the code.

      If you have concrete technical feedback or security issues, I’d genuinely appreciate it.

        • chicken@lemmy.dbzer0.comEnglish
          1·
          2 months ago

          because I don’t know jackshit about coding and I am not gonna pretend I do.

          But if OP does know and applies that knowledge to what they are doing, it’s not the same thing and doesn’t make sense to have the same disclaimer.

        • Serinus@lemmy.worldEnglish
          1·
          2 months ago

          It’s not realistic to expect no AI assistance in coding in 2026.

          It’s also not a stand-in for a human. There’s a huge field of gray where it’s unclear how much of it was fully vibe coded vs how much is carefully hand reviewed and/or written.

          I’ve been a professional developer for decades and I’ve done both. Obviously I’ve hand coded stuff for many years. The fully vibe coded stuff is personal, to test and learn the capabilities of the tech. My professional stuff I watch much more closely, and I’m much more targeted in what I’m having the AI do.

          That said, if I were gonna use this I’d actually review the code. I’m not recommending this guy’s stuff, but you can’t rule it out on the basis of ai assistance alone.