You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JSON input file should an object with the keys being the name of the Action, and the value being an array of the commits you are interested in.
39
+
40
+
Use the Action name in the format `owner/repo` or `owner/repo/path`, where `path` can contain any number of slashes.
41
+
42
+
You can express some wildcards - use `*` after the first `/` in the Action to include all repositories under the owner, and use `*` in the commit array (or leave it empty) to include all commits.
43
+
44
+
An Action name given without a path will match any Action in that repository, whether or not it has a path. You can also explictly use `*` in the path to match any path.
45
+
34
46
### find_compromised_secrets.js
35
47
36
48
> [!NOTE]
37
-
> This is relevant only to secrets leaked after the `tj-actions/changed-files` and `reviewdog` compromises in March 2025.
38
-
39
-
This script takes the output of `audit_workflow_runs.js` and searches for secrets that were leaked in those workflow runs.
49
+
> This is relevant only to secrets leaked because of the `tj-actions/changed-files` and `reviewdog` compromises in March 2025.
40
50
41
-
You should take the output from the single-line JSON file for any known-compromised Actions and run it through this script.
51
+
This script takes the structured single-line JSON output of `audit_workflow_runs.js` (not the convenience CSV output) and searches for secrets that were leaked in those workflow runs.
0 commit comments