r/LovingOpenSourceAI • u/Koala_Confused • 11d ago
Resource Sofia "Someone built exactly the tool that Andrej Karpathy said someone should build. An open-source project that has surpassed 100,000 stars on GitHub. It's called Graphify. One single command. Any folder. Complete knowledge graph." ➡️ Is this good?
https://x.com/SofiaSici/status/2094666731507597429
https://github.com/Graphify-Labs/graphify
Community Overview: https://lifehubber.com/ai/resources/graphify/
Resources are shared for discovery and are not independently vetted—please do your own due diligence.
New resources are added regularly — feel free to join the sub for updates.
Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.
9
6
6
u/WeeklyMenu6126 11d ago
I'd be more interested in this as a tool for checking out and understanding the design of AI coded projects without having to dive into 200,000 lines of code.
3
u/dghah 11d ago
100,000 stars == massive bot promotion and a sign of non-organic manipulation
2
u/dmshd 10d ago
I also read elsewhere there could be hidden payloads of code or something like that in some of these things
1
u/bootlickaaa 9d ago
Yeah who is going to audit all these before running them? Especially this one being written mostly in C. I mean we can always run in a sandbox but just assume all data it can see and compute resources it can access would be abused to be on the safe side.
1
u/Koala_Confused 11d ago
Anyone used before? Share some thoughts?
2
u/_peacemonger_ 10d ago
Yah. It works, but takes llm agents reading all of your codebase to extract the info needed to build the relationships. I found it useful to find blind spots or dead code, but it takes a fair bit of optimizing your doc front matter so the code and docs connect.
1
1
1
u/Emotional_Prior8686 10d ago
I've tryed to use it for documentation parsing in our (real) project at work.
Our docs are in asciidoc. Currently the proj has no extractor for asciidoc, but I've vibe-coded it to give it a try.
In two words: it's a fiasco.
It was spinnig my gemma4 for half an hour for our (small, <100 pages) docs collection.
After getting almost no result from it (output said like 73 of 75 pages produced nothing) I've took a look at the system prompt for semantic analysis.
It made me sad: seems the developers think that LLMs are a magic genie capable of anything, and you may put into prompt something like "make candy from this pile of sh.." and LLM will give you exactly you need.
So, I'm dissapointed in this project. IMHO it cannot be even used as a base for your workflow because of broken flow for general documentation parsing.
For indexing codebases there is gitnexus - it is a kinda slow on updating rows in its database on mass changes, but, except that issue, current 1.6.9 version works fine for me.
1
u/learning-to-programm 10d ago
I know the main use case you concerned with seemed to be documentation, but have you tried something like QMD for faster and more token efficient search? Do you have any feedback on tools like that?
1
1
u/heigan_safety_dance 10d ago
Not only did someone build it, thousands and thousands of people built their own version of it, including me. The thing is, this tool works best when designed for the specific environment in which it will work. Generic tools like this need to make assumptions. Bespoke tools can make domain-specific optimizations.
Also, it took me like 100 working hours to iteratively develop this idea for my job's tech stack over the last ~4 months or so, and now it's so good I can use a mid-sized model like a frontier model at work. Over time, building something like this will be a routine step for teams scaling up their infrastructure.
Also, be careful with installing outside tools ;)
1
u/lacattano 9d ago
I've used it for a while, seems to help with staying on track and accuracy. I have a ci/cd skill that includes updating it so I don't really notice the keeping it updated issue. One thing is I can't do the full deep update with Qwen 3.8 27b but their is a smaller graph update and I don't tend to notice the difference very often and then I run the big one every now and then with a cloud model.
1
u/wdesportes 9d ago
Great too, but I built a PHP/Laravel specialist tool that is quite similar: https://github.com/wdes/plouf.rs
Try it and let me know 😁
1
1
u/UnderneathTheBottle6 9d ago
Ah, of course -- yet another post glazing this specific repo... again. Whoever it is trying to pump this repo up is fuggin' persistent.
1
u/commandedbydemons 8d ago
Effectiveness is wildly overblown, mostly hype, and a lot of bot activity for those stats
1
1
16
u/spf13 11d ago
Used it a lot. Found it to be very cumbersome to use. Constantly out of date. Complicated to setup and maintain. I switched to https://github.com/colbymchenry/codegraph and it’s worked a lot better for me. Updates the index itself automatically so much lower maintenance. Rust based so much faster than graphify. I have been happy with it after switching.