PROC-66: Align providers and extensions with astronomer images #13
Acuion
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
security_scans.yml
on: pull_request
iac_security_scan
/
iac_security_scan
41s
dependency_vulnerability_scan
/
dependency_security_scan
20s
Annotations
1 error and 3 warnings
|
dependency_vulnerability_scan / dependency_security_scan
Process completed with exit code 1.
|
|
[MEDIUM] Unpinned Actions Full Length Commit SHA:
.github/workflows/manual-build-and-publish.yaml#L71
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
|
|
[MEDIUM] Unpinned Actions Full Length Commit SHA:
.github/workflows/manual-build-and-publish.yaml#L49
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
|
|
[MEDIUM] Unpinned Actions Full Length Commit SHA:
.github/workflows/manual-build-and-publish.yaml#L56
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
|