Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle What I Built Maintainers usually find out a dependency is dead when something breaks. DepExit finds the risky ones up front, asks Gemma 4 for a replacement plan for each, and then refuses to trust the plan until
Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle Submission 馃捀
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle
Maintainers usually find out a dependency is dead when something breaks. DepExit finds the risky ones up front, asks Gemma 4 for a replacement plan for each, and then refuses to trust the plan until it has applied it to an isolated copy, reinstalled everything and run the tests. Each dependency gets a Dependency Exit Capsule: a JSON record, a readable Markdown page and a patch. Every fact in it is tagged OBSERVED, MEASURED, AI-SUGGESTED or AI 路 VERIFIED, so you can see which claims came from files, which came from running code, and which are only the model's suggestion.
Who would pay: freelancers and small agencies who take on neglected Python codebases, and small teams who inherited one. Today that audit means a day or two of reading changelogs and guessing. DepExit turns it into a 13-minute run that produces a report you can hand to a client and a patch you can review. A wrong migration in a healthy project is worse than none, so the part worth paying for is that nothing is claimed as fixed until it has been run.
A complete run on the organizer's LinkWatch repo is committed in examples/linkwatch-run/. Open report.html after cloning, or read SUMMARY.md on GitHub. It was produced on 15 October 2026 with gemma-4-31b-it through the Gemini API and took 13 minutes.
Evidence-first dependency exit planning, with Gemma 4 proposing and execution deciding.
Hacktoberfest Hack Day Mumbai 脳 ISTE KJSSE 2026 路 Track 1: Gemma 4 路 Dependency Resilience 路 Team 404_TeamNotFound
DepExit points at a Python repository, finds the dependencies that put it at risk, asks Gemma 4 how to get out of each one, and then refuses to believe the answer until it has applied the change to an isolated copy, reinstalled everything, and run the tests. What comes out is a Dependency Exit Capsule for every dependency: a JSON record, a readable Markdown page and a patch, in which every single fact is tagged with where it came from.