---
title: "Discussion on \"Why You Should Not Use The Version Tag Or Branch Name When Using GitHub Actions\" | Hashnode"
description: "Discussion on \"Why You Should Not Use The Version Tag Or Branch Name When Using GitHub Actions\". The Secure Way to use GitHub Actions"
url: "https://hashnode.com/posts/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions/6031479c72a689446db3e025"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why You Should Not Use The Version Tag Or Branch Name When Using GitHub Actions](https://blog.natterstefan.me/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions?utm_source=hashnode&utm_medium=feed)

The Secure Way to use GitHub Actions

Feb 20, 2021 · 4 min read · blog.natterstefan.me  
Read the article

-   [#github](https://hashnode.com/tag/github)
-   [#github-actions-1](https://hashnode.com/tag/github-actions-1)
-   [#security](https://hashnode.com/tag/security)

## Written by

[Stefan Natter](https://hashnode.com/@natterstefan)

@natterstefan · Austria

  
[View profile](https://hashnode.com/@natterstefan)

I am interested in and talking about JavaScript, ReactJS, NodeJS, and Software Engineering.

Hey 👋🏻, I am a Software Engineer from Austria 🇦🇹. I am interested in, write about, and develop (open source) software solutions for and with JavaScript, TypeScript, ReactJs, and NodeJS. You can see what I am currently up to on natterstefan.me . In the past, I was Product Owner of RAWR , Growth Hacker at the Speedinvest Startup Studio and Online Advertising Manager. Check out my LinkedIn profile for more details. 📬 Get in touch Twitter: twitter.com/natterstefan Blog: dev.to/natterstefan Web: natterstefan.me LinkedIn: linkedin.com/in/natterstefan 📧 Sign up for my newsletter .

## Responses 1

Markdown supported · ⌘↵ to post

[Corey Seliger](https://hashnode.com/@seliger)

[May 28, 2022](https://hashnode.com/posts/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions/6031479c72a689446db3e025/comment/6292503b0989e6b52feafcb6)

The security concern makes sense. However, why not fork the action and have complete control, refreshing from upstream at your leisure and comfort? What if the author decided to no longer host that code?
