<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: komil Hassan</title>
    <description>The latest articles on DEV Community by komil Hassan (@komil_hassan_c9ce5cad3bbb).</description>
    <link>https://dev.to/komil_hassan_c9ce5cad3bbb</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204300%2F87c68a18-b755-4685-bf03-4aa5d98cadbc.jpg</url>
      <title>DEV Community: komil Hassan</title>
      <link>https://dev.to/komil_hassan_c9ce5cad3bbb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/komil_hassan_c9ce5cad3bbb"/>
    <language>en</language>
    <item>
      <title>AI Wrote Your Code. Nobody Checked It for Security Holes — So I Built a Scanner</title>
      <dc:creator>komil Hassan</dc:creator>
      <pubDate>Sun, 08 Nov 2026 19:40:26 +0000</pubDate>
      <link>https://dev.to/komil_hassan_c9ce5cad3bbb/ai-wrote-your-code-nobody-checked-it-for-security-holes-so-i-built-a-scanner-53ih</link>
      <guid>https://dev.to/komil_hassan_c9ce5cad3bbb/ai-wrote-your-code-nobody-checked-it-for-security-holes-so-i-built-a-scanner-53ih</guid>
      <description>&lt;p&gt;Vibe coding is fast. You describe it, Cursor or ChatGPT or v0 writes it, and it works. What nobody does in that loop is read the code for security.&lt;/p&gt;

&lt;p&gt;That's how secrets end up in production. I keep seeing the same holes in AI-generated code: API keys hardcoded in the source, SQL queries built with string concatenation, user input rendered straight into the page, CORS set to allow everything, no security headers at all, passwords hashed with MD5.&lt;/p&gt;

&lt;p&gt;The AI doesn't do this to hurt you — it just writes the shortest path to "it works." Security isn't in the prompt unless you put it there.&lt;/p&gt;

&lt;p&gt;So I built AIScan (&lt;a href="https://aiscan.akclnt.com" rel="noopener noreferrer"&gt;https://aiscan.akclnt.com&lt;/a&gt;) — a free scanner for AI-generated code. Paste your code or upload a file (or a whole project as a ZIP) and it runs 32 checks on a single file, 35 checks on a full project: exposed API keys, SQL injection, XSS, insecure CORS, missing security headers, weak password hashing, and more.&lt;/p&gt;

&lt;p&gt;Two things I deliberately kept:&lt;/p&gt;

&lt;p&gt;Find-only, no auto-fix. It tells you what's wrong and gives you a copy-paste fix prompt to hand back to your AI. You stay in control — nothing gets rewritten behind your back.&lt;br&gt;
Nothing leaves your browser on a single-file scan. Your code isn't uploaded anywhere to be checked.&lt;br&gt;
There's also a daily security news page if you want to keep up with what's breaking, and a Pro Report ($19, waitlist) and a Done-For-You review ($149) if you want a human to go through it.&lt;/p&gt;

&lt;p&gt;My question for you: what's the worst security hole you've found in AI-generated code? The one that made you stop and re-read everything it wrote.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>coding</category>
      <category>security</category>
      <category>tools</category>
    </item>
    <item>
      <title>I Audited the Biggest Free API List. ~20% of It Is Broken.</title>
      <dc:creator>komil Hassan</dc:creator>
      <pubDate>Sun, 08 Nov 2026 19:31:47 +0000</pubDate>
      <link>https://dev.to/komil_hassan_c9ce5cad3bbb/i-audited-the-biggest-free-api-list-20-of-it-is-broken-46ah</link>
      <guid>https://dev.to/komil_hassan_c9ce5cad3bbb/i-audited-the-biggest-free-api-list-20-of-it-is-broken-46ah</guid>
      <description>&lt;p&gt;I needed free APIs for a project, so I went looking. Every list I found had the same problem: entries that say "free" but aren't.&lt;/p&gt;

&lt;p&gt;Someone ran hourly pings against the public-apis repo on GitHub (350k+ stars) and found conservatively 15–25% of entries degraded — dead, paywalled, moved endpoints, or rate-limited far below what the docs claim. The casualties are familiar names: Dark Sky (killed Dec 2022 after the Apple acquisition), Twitter's v1.1 free tier (paywalled July 2023, $100/mo minimum), Reddit's free API (effectively killed June 2023), Yahoo Finance v7 (dead since 2017), Weather Underground's free tier (sunset 2019).&lt;/p&gt;

&lt;p&gt;Free LLM APIs decay even faster. One check in September 2026 found half of them dead after just two months — Cerebras returning "402 Payment Required", Gemini models disappearing from the catalog, Groq keys going 401.&lt;/p&gt;

&lt;p&gt;The pattern is always the same: a startup launches a generous free tier, the tier becomes a real AWS line item, then monetization or an acquisition kills it. And nobody files removal PRs — removing a dead entry doesn't grow the catalog, so the dead ones just stay listed.&lt;/p&gt;

&lt;p&gt;"Free" itself has become a weasel word. It can mean genuinely free, free-after-you-add-a-card, free-until-we-change-our-minds, or free-behind-a-login-wall. A list that doesn't verify can't tell the difference.&lt;/p&gt;

&lt;p&gt;That's why I built FreeAPIs (&lt;a href="https://freeapis.akclnt.com" rel="noopener noreferrer"&gt;https://freeapis.akclnt.com&lt;/a&gt;) — a directory that only lists APIs with a real free tier and live-tests the endpoints, so dead ones drop off instead of lingering. 1,769 APIs in there now.&lt;/p&gt;

&lt;p&gt;My question for you: what's a free API you've used for years that has genuinely stayed free? I'm collecting the survivors.&lt;/p&gt;

&lt;p&gt;Sources: the public-apis audit (&lt;a href="https://dev.to/a10ayassine/i-audited-the-350k-star-public-apis-list-with-hourly-pings-20-of-it-is-broken-4447"&gt;https://dev.to/a10ayassine/i-audited-the-350k-star-public-apis-list-with-hourly-pings-20-of-it-is-broken-4447&lt;/a&gt;) and the free-LLM-API check (&lt;a href="http://dev.to/orca_forge/half-of-free-llm-apis-were-dead-after-2-months-o14"&gt;http://dev.to/orca_forge/half-of-free-llm-apis-were-dead-after-2-months-o14&lt;/a&gt;)&lt;/p&gt;

</description>
      <category>api</category>
      <category>backend</category>
      <category>github</category>
      <category>programming</category>
    </item>
    <item>
      <title>We Checked 1,600+ Free APIs. 254 Were Already Dead.</title>
      <dc:creator>komil Hassan</dc:creator>
      <pubDate>Sat, 24 Oct 2026 08:55:26 +0000</pubDate>
      <link>https://dev.to/komil_hassan_c9ce5cad3bbb/we-checked-1600-free-apis-254-were-already-dead-3jmd</link>
      <guid>https://dev.to/komil_hassan_c9ce5cad3bbb/we-checked-1600-free-apis-254-were-already-dead-3jmd</guid>
      <description>&lt;p&gt;Every tutorial you have ever followed starts the same way: "just use this free API." Nobody tells you the second half of that sentence — that the API might have died two years ago.&lt;/p&gt;

&lt;p&gt;I run &lt;a href="https://freeapis.akclnt.com" rel="noopener noreferrer"&gt;AKCLNT Free APIs&lt;/a&gt;, a directory of free APIs. Last month we did something the famous lists never do: we actually &lt;em&gt;checked&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The method (steal it, it is simple)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Curated core (111 APIs):&lt;/strong&gt; a real GET request to a documented endpoint. One retry. Status, response time, and the response body itself are captured and published.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wider catalog (1,600+ APIs):&lt;/strong&gt; a link check. The official site must answer like a living service — 2xx/3xx, or a login page that proves the service exists. Silence, 404s and 5xx after retries = dropped, not listed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weekly re-checks.&lt;/strong&gt; A list is a snapshot; APIs are living things. So the checks run every week, and the results are public per API — status history, uptime, health score.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What we found
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;254 dead links refused entry&lt;/strong&gt; since tracking began. Not "deprecated." Dead. Sites that no longer answer at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;82 APIs verified live&lt;/strong&gt; with real endpoint requests at the latest check, and 4 down right now — shown, not hidden.&lt;/li&gt;
&lt;li&gt;The most common way a free API dies is not dramatic: the startup folds, the side project loses its hosting, the free tier gets acquired into oblivion. The tutorial that recommended it lives on forever.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The APIs that survive
&lt;/h2&gt;

&lt;p&gt;The pattern is almost boring: the survivors are boringly well-run. Open-Meteo (weather, no key at all), REST Countries, PokeAPI, JSONPlaceholder, Frankfurter (ECB currency data, no key) — the ones run by institutions or by maintainers who treat uptime as the product.&lt;/p&gt;

&lt;p&gt;If you are picking an API for a project, here is the checklist I now use:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Does it answer right now?&lt;/strong&gt; (Not "did a blog post say it works in 2021.")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is there a status history?&lt;/strong&gt; One green check means nothing. Twenty weekly checks mean something.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What happens when it breaks?&lt;/strong&gt; A public status page, or silence?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keyless or free-key?&lt;/strong&gt; Keyless is zero friction for prototypes. A free key is usually &lt;em&gt;more&lt;/em&gt; reliable for production, because rate limits are per-user.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Take the data
&lt;/h2&gt;

&lt;p&gt;The whole catalog is open:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Browse it: &lt;a href="https://freeapis.akclnt.com" rel="noopener noreferrer"&gt;freeapis.akclnt.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Raw JSON: &lt;a href="https://freeapis.akclnt.com/data.json" rel="noopener noreferrer"&gt;freeapis.akclnt.com/data.json&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Dataset (CSV + JSON with check history): on Kaggle and HuggingFace — search "Free APIs Directory"&lt;/li&gt;
&lt;li&gt;Every API has a watch feed — subscribe and get an item the week its status changes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And if you maintain a free API: your listing page has a live badge you can put on your README. It always shows the status from our latest check. No cost, no account.&lt;/p&gt;

&lt;p&gt;The next census lands in November. If your favorite free API is missing — or dead — tell me in the comments and I will check it myself.&lt;/p&gt;

</description>
      <category>api</category>
      <category>webdev</category>
      <category>opensource</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
