Skip to content

Security: pin GitHub Actions to SHA hashes - #14

Merged
afsmeira merged 1 commit into
masterfrom
security/pin-actions-to-sha
Mar 25, 2026
Merged

Security: pin GitHub Actions to SHA hashes#14
afsmeira merged 1 commit into
masterfrom
security/pin-actions-to-sha

Conversation

@jorgebraz

Copy link
Copy Markdown
Contributor

Pins all GitHub Actions from mutable tags/branches to immutable SHA hashes.

This prevents supply chain attacks like the TeamPCP/Trivy incident (March 2026), where attackers force-pushed tags to point at malicious commits.

Auto-generated by the Codacy security audit script.

Replaces mutable tag/branch references with immutable SHA hashes
to prevent supply chain attacks (ref: TeamPCP/Trivy March 2026).

Actions left as tags: 0
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes. Give us feedback

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

The PR attempts to harden the repository's security posture by pinning GitHub Actions to immutable SHA-1 hashes. Codacy analysis confirms the changes are up to standards with no new quality or complexity issues. However, there are significant gaps in the implementation regarding the acceptance criteria: the specific SHA pins for 'actions/github-script' and the 'atlassian/gajira' suite are currently missing or do not match the required security baseline. These gaps should be addressed before merging to satisfy the security requirements of the project.

About this PR

  • The following actions are not correctly pinned to the required SHA hashes: 'actions/github-script' (6e5ee1d), 'atlassian/gajira-login' (90a5995), 'atlassian/gajira-create' (c0a9c69), and 'atlassian/gajira-comment' (8ec356b). Please ensure these specific versions are used across the workflow files to meet the security hardening requirements.

Test suggestions

  • Verify that 'actions/github-script' is consistently pinned to SHA 6e5ee1d across all workflow files.
  • Verify that 'atlassian/gajira-login' is pinned to SHA 90a5995 across all workflow files.
  • Verify that 'atlassian/gajira-create' is pinned to SHA c0a9c69 in issue creation workflows.
  • Verify that 'atlassian/gajira-comment' is pinned to SHA 8ec356b in the comment workflow.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that 'actions/github-script' is consistently pinned to SHA 6e5ee1d across all workflow files.
2. Verify that 'atlassian/gajira-login' is pinned to SHA 90a5995 across all workflow files.
3. Verify that 'atlassian/gajira-create' is pinned to SHA c0a9c69 in issue creation workflows.
4. Verify that 'atlassian/gajira-comment' is pinned to SHA 8ec356b in the comment workflow.

🗒️ Improve review quality by adding custom instructions

@afsmeira
afsmeira merged commit b5692a4 into master Mar 25, 2026
1 check passed
@jorgebraz
jorgebraz deleted the security/pin-actions-to-sha branch March 25, 2026 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants