Git analytics that works across GitHub, GitLab, and Bitbucket
I built Gitmore. Connects via webhooks, tracks commits and PRs, and gives you one dashboard. AI answers questions about activity, sends weekly reports to Slack/email. Connect agent to slack which answers your questions directly from your workspace. https://gitmore.io (free for 1 repo) Anyone else juggling multiple Git platforms?
24 comments
Wild how many folks vibe code a thing and then claim to have created something that they ask us to plug into critical infrastructure with the ability to read, write, and execute.
No thanks.
No thanks.
We have deifinitely used AI just like everyone else, but we are senior 4+ years of experience. Also Gitmore doesn't have the ability to read your code nor execute or write. We only get data from webhooks which are commits/ PR info with no code. Thanks for your Attention.
"Just like everyone else" is a crazy take on AI, no part of AI has ever touched my production environment nor will it ever. 4 years is also not senior at anything in my experience.
Of course i haven't asked every dev that exists whether they use AI or not but most companies/devs does, you choose to not use it, good luck with that.
You may be mistaken. There is a good (and growing) number of folks who have noticed that vibe-coding isn’t always the right fit. There have also been a number of instances where AI agents have destroyed production environments.
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.
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 haven't said that the app is fully vibe coded, i said we used AI. The app is not fully vibecoded but we have used AI assistance and i am aware of the security concerns that comes with github/ slack implementation. Its a question of how you use AI in your app the system is fully designed by us so we know how it exactly behaves and how the data and tokens are stored/ exchanged.
You mention tokens, what else is in your threat model? Is your AI functionality a custom model?
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.
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.
Where does this say it's vibe coded?
You can pretty well infer that is the case from someone claiming to be operating at a senior level with 4 years of experience.
your privacy argument is valid but it is true for all new startups. If your repository on github than you are already giving your data to big corp why do u trust them?
Backup your allegation on vibe code, i don't see any mention of vibe coding on website.
Who said anything about privacy? Sure, privacy is a concern, but I’m more worried about a vibe-coded app produced by an inexperienced team without the assistance of a security team causing a breach, or an agent-caused outage.
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.
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.
It's more wild that everyone's first reaction to seeing a new product is "probably vibe-coded AI slop". We held so little respect for the craft of software engineering that AI managed to kill it completely in about two years.
The fact that the websites pictures are all AI generated isn't exactly a great sign.
Pictures on websites have always been either stolen from other sites a long time ago, then stock pictures from Unsplash or Pexels for a while, and now they're AI because that's just the easiest way to get images now. I don't think it's fair to developers to assume that the ones using AI generated images are also vibe-coding the software though. It's not like the ones writing hand-crafted artisanal code are also out with their cameras taking pictures for the website after all.
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.)
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.)
I think it's very fair because it's a metric of how much effort and money has been invested into the project.
Sites with generic stock photos were always a bad sign when dealing with websites in the past as well.
Sites with generic stock photos were always a bad sign when dealing with websites in the past as well.
They could at least not keep a picture that shows them with eleven fingers, though (https://web.archive.org/web/20251231080727/https://www.gitmo...)
From the FAQ:
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.
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.
I've raised this exact point to many team leads throughout my career.
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.
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.
Try it https://gitmore.io
Have you considered scanning open source repos for free? I would like to an example of an actual reports without connecting anything.
It is possible to have another analytics that connects to Trello or Calendar to tell me "Project is finished"?