Right now security vulnerability reporting is broken when a workflow uses a floating tag, branch or sha.
The lock file is a perfect source for the dependency graph to record the dependencies.
The built-in narrowing could also report the actual versions so that de vulnerability reporting works.
I currently have an action that implements this based on parsing the workflows directly:
https://github.com/jessehouwing/actions-dependency-submission
It would be awesome if the "automatic dependency submission" would actually use the existing lock file or generate a ephemeral lockfile.
Right now security vulnerability reporting is broken when a workflow uses a floating tag, branch or sha.
The lock file is a perfect source for the dependency graph to record the dependencies.
The built-in narrowing could also report the actual versions so that de vulnerability reporting works.
I currently have an action that implements this based on parsing the workflows directly:
https://github.com/jessehouwing/actions-dependency-submission
It would be awesome if the "automatic dependency submission" would actually use the existing lock file or generate a ephemeral lockfile.