mohith
158 posts

mohith
@MohithAchu
GSoC’26 @ RUXAILAB | be delusional
Kerala, India Katılım Temmuz 2023
154 Takip Edilen34 Takipçiler
Sabitlenmiş Tweet
mohith retweetledi


@letsbuilddd i open linkedin and X all i see is “i dropped out of…”
Its like a trend now
English

@daleverett @daltonmeon @damienhe @evokoa_ai @InsForge_dev @supabase @neondatabase This is insanely useful , congrats on the launch...
English
mohith retweetledi

Today, we’re launching pgGraph: an Apache open-source graph traversal engine for Postgres, written in Rust 🦀
When we started Evokoa, we kept running into the same wall every serious agent team eventually hits:
> Agents need to reason across relationships.
> But graph DBs are expensive AF, and suck to use.
So, we built pgGraph around a simple, single idea:
Postgres should stay the source of truth, and the graph engine should live beside it.
pgGraph does something different.
> It keeps the rows in Postgres,
> Compiles the topology around them,
> Creates a virtual graph layer using CSR-style adjacency arrays.
We're making your existing postgres database graph-traversable for agents without any of the usual BS.
> No recursive join hell.
> No ETL pipeline.
> No second source of truth.
> Blazing fast performance
pgGraph is already live in production workflows across RevOps, healthcare, and visa services.
We’re open-sourcing it because graph traversal should become a default primitive in the agent stack, not an enterprise migration project.
Treat Postgres as a graph.
Zero data migration.
This is what Apache AGE should have been.
Docs + Repo below.

English
mohith retweetledi

@IntCyberDigest attacks like these will lead to the end of opensource
English

🚨 How the TanStack npm attack actually happened:
1. Attacker opened a normal-looking pull request (#7378) on the TanStack repo.
2. GitHub automatically ran CI tests on that PR.
3. Code inside the PR stole the workflow's GitHub Actions Cache write token during the test run.
4. The attacker used that token to plant poisoned files in the shared build cache. The PR could be closed afterwards. The poisoned cache stays.
5. The official release workflow later pulled from the cache, baked the malicious files into the build, and signed and published 84 malicious package versions to npm.
Adnan Khan@adnanthekhan
This attack leveraged GitHub Actions Cache Poisoning. Payload deployed here: github.com/TanStack/route… It looks like it detonated here: #step:26:2" target="_blank" rel="nofollow noopener">github.com/TanStack/route…
English

@letsbuilddd if you need someone who says “we should build that” every 8 minutes
English














