Actions joins the dependency graph
The dependency graph on GitHub has long mapped the open source packages a repository pulls in from package managers like npm, NuGet, Maven, and RubyGems. Now it covers another major class of project dependencies: GitHub Actions workflows.
For any repository that uses Actions, the dependency graph under the Insights tab now lists your Actions workflows alongside traditional dependencies. That means you can see every action your workflows reference in one place, rather than hunting through YAML files.
Seeing who uses your action
The reverse direction is useful for maintainers too. If you publish an action, the Dependencies tab shows you the list of repositories that depend on it. The same information drives the "Used By" counter on your repository homepage. Note that private repositories using your action are not included in either count.
If one repository hosts multiple packages or actions, you can choose which one appears on the repository homepage by changing the displayed "Used By" package, so you can highlight the package you want others to find.
The dependency graph underpins GitHub's supply chain security tooling, since knowing what you depend on is the first step to securing it. You can set up Dependabot version updates to keep Actions dependencies current automatically. More supply chain improvements targeting Actions are scheduled on the public roadmap.
