<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vendor-Risk on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/vendor-risk/</link><description>Recent content in Vendor-Risk on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Jul 2026 12:23:02 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/vendor-risk/index.xml" rel="self" type="application/rss+xml"/><item><title>HashiCorp CEO labels Terraform community-building efforts 'Malicious'</title><link>https://curadevops.metacog.co.kr/insights/2026-07-22-hashicorp-ceo-called-their-community-building-for-terraform/</link><pubDate>Wed, 22 Jul 2026 12:23:02 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-22-hashicorp-ceo-called-their-community-building-for-terraform/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The CEO&amp;rsquo;s characterization of community engagement as adversarial adds cultural context to HashiCorp&amp;rsquo;s posture following the BSL relicensing — useful background when evaluating long-term vendor risk or the case for OpenTofu migration, but no new fact or deadline changes the decision calculus today.&lt;/li>
&lt;/ul></description></item><item><title>Terraform Registry Terms of Service Updated</title><link>https://curadevops.metacog.co.kr/insights/2026-07-22-the-terraform-registry-terms-of-service-have-been-updated/</link><pubDate>Wed, 22 Jul 2026 12:23:02 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-22-the-terraform-registry-terms-of-service-have-been-updated/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> The updated ToS may restrict how the Terraform Registry can be consumed, particularly by tooling or automation that competes with or mirrors registry content. Review current Terraform and provider-download patterns against the new terms and evaluate whether a migration to OpenTofu or a self-hosted registry should be scoped this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Pipelines that pull Terraform providers and modules via the public registry could be indirectly affected if the new ToS introduces usage restrictions on automated clients; worth monitoring, but no concrete pipeline action is required yet.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> A ToS change on a registry that most Terraform-standardized orgs depend on is a direct vendor-risk signal; evaluate whether current registry consumption falls under any newly restricted terms and assess OpenTofu as a contingency before any enforcement timeline is announced.&lt;/li>
&lt;/ul></description></item></channel></rss>