<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LaTeX CV Pipeline on SoloSoft</title><link>https://www.solosoft.dev/tags/latex-cv-pipeline/</link><description>Recent content in LaTeX CV Pipeline on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/latex-cv-pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>50,406 Stars, 16,937 Forks, 187 Watchers: Auditing the AI Job-Search Framework Where Two Privacy Leaks Were Already Filed by Real Users</title><link>https://www.solosoft.dev/post/ai-job-search-50406-stars-two-privacy-leaks-audit/</link><pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/ai-job-search-50406-stars-two-privacy-leaks-audit/</guid><description>&lt;p&gt;A geophysicist loses his job in late 2025, builds a Claude Code workflow to run his own search, applies 69 times, gets 20 first interviews, signs one contract, and open-sources the machinery in March 2026. Seven months later the repository has 50,406 stars. That story is on the README, in the first screen, and it is the reason people fork it.&lt;/p&gt;
&lt;p&gt;The story that is not on the README is in the issue tracker. Between August 19 and August 28, two different users reported that this workflow had already published personal data to GitHub — once through the fork the quick start tells you to create, once through a &lt;code&gt;gh&lt;/code&gt; default-repository behaviour that files your application notes on someone else&amp;rsquo;s public tracker. I cloned the repo, ran its own checks, sampled 120 of its forks, and read both issues. What follows is what the numbers and the code actually support.&lt;/p&gt;</description></item></channel></rss>