<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secret-Scanning on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/secret-scanning/</link><description>Recent content in Secret-Scanning on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Jul 2026 15:50:13 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/secret-scanning/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Secret Scanning detector types get renamed for clarity</title><link>https://curadevops.metacog.co.kr/insights/2026-07-11-clearer-names-for-secret-scanning-detector-types/</link><pubDate>Sat, 11 Jul 2026 15:50:13 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-11-clearer-names-for-secret-scanning-detector-types/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> If your pipelines parse or display GitHub secret scanning output, the renamed detector type labels may affect dashboards or tooling that filters by those names — low urgency, no deadline.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>