No thanks.
FWIW I don't disagree with you. I also assume people are vibe-coding things. I just don't think it's fair to assume that means the devs are taking that code and firing it straight up to a production server. They're probably fixing the problems and making it better. I know I do that in my code (most of the time.)
Sites with generic stock photos were always a bad sign when dealing with websites in the past as well.
It seems more likely that such a team would have poor security controls, insufficient staff training, and may themselves be threat actors.
For an enterprise tool like this, one which integrates with two or more other sensitive systems, I would expect a vendor to have some manner of independently audited security certification such as ISO-27001.
In your 4+ years of “experience,” have you acquired the experience necessary to protect anybody’s GitHub, slack, or any other enterprise systems from the numerous security concerns that you’re just hand-waiving away?
Not all “devs” use AI, and very few companies would trust a fully vibe-coded enterprise system plugin with no security team, no enterprise support, no GDPR documentation, and all fielded by a team with fewer than five years of experience.
That seems like the path to breaches, or to having an agent take destroy sensitive systems, or both.
I am concerned that you haven’t adequately explored and mitigated security and reliability risks involved here before asking folks to YOLO your app into their critical infrastructure.
Yes, many teams use Gitmore to eliminate or reduce daily standups. Instead of synchronous meetings where developers report what they worked on, Gitmore automatically extracts this information from Git activity.
If your standups are just reports of what code the dev worked on the previous day then that sounds like a great thing to automate away, and Gitmore is likely a great way to do that.
However, that also means your standups are a pointless waste of time, and the solution shouldn't be to automate the pointless waste of time, it should be to improve your standups so they're actually useful. Rather than just saying what code the devs wrote you could use the time to discuss problems that came up, where people are blocked or where they believe they might be blocked in the next couple of days, or just have a bit of a check-in with everyone to see if they're feeling good about their progress. Standups shouldn't be simple progress reports; they should be an opportunity for the team to come up for air and chat with one another. If you're missing that then you're not really a team, you're just a bunch of individual devs working in the same domain. That sucks. The solution isn't removing the meeting with automation.
Yet, they unanimously said, they are interested or need to know the progress.
I can't say if thats what they have to report to their managers, but I assume it's something you won't be able to fix from bottom-up.
Does gitmore just call GitHub API or counts by commits manually?