Skip to content

chore(stepsecurity): apply security best practices#20

Merged
ali-kafel merged 6 commits into
masterfrom
chore/GHA-041845-stepsecurity-remediation
Nov 5, 2025
Merged

chore(stepsecurity): apply security best practices#20
ali-kafel merged 6 commits into
masterfrom
chore/GHA-041845-stepsecurity-remediation

Conversation

@stepsecurity-app

Copy link
Copy Markdown
Contributor

Summary

This pull request has been generated by StepSecurity as part of your enterprise subscription to ensure compliance with recommended security best practices. Please review and merge the pull request to apply these security enhancements.

Security Fixes

Harden Runner

Harden-Runner is an open-source security agent for the GitHub-hosted runner to prevent software supply chain attacks. It prevents exfiltration of credentials, detects tampering of source code during build, and enables running jobs without sudo access.

Least Privileged GitHub Actions Token Permissions

The GITHUB_TOKEN is an automatically generated secret to make authenticated calls to the GitHub API. GitHub recommends setting minimum token permissions for the GITHUB_TOKEN.

Pinned Dependencies

Pinning GitHub Actions to specific versions or commit SHAs ensures that your workflows remain consistent and secure.
Unpinned actions can lead to unexpected changes or vulnerabilities caused by upstream updates.

Feedback

For bug reports, feature requests, and general feedback; please create an issue in step-security/secure-repo or contact us via our website.

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
@ali-kafel

Copy link
Copy Markdown
Member

🔒 Automated Update: The harden-runner configuration has been updated.

Changes:

  • Updated egress-policy from audit to block
  • Added policy: global-allowed-endpoints-policy
  • Added permissions: id-token: write to jobs using harden-runner (if not already present)

This change was applied automatically to workflow files in this PR.

@akshay29595

Copy link
Copy Markdown

There's a workflow error in the release workflow

[Invalid workflow file: .github/workflows/release.yml#L16](https://github.com/circlefin/circle-ooak/actions/runs/19081026415/workflow)
The workflow is not valid. .github/workflows/release.yml (Line: 16, Col: 3): Error calling workflow 'circlefin/circle-ooak/.github/workflows/release-test.yml@1355c641574153b3820f56ec95ea303bf8bd1bd4'. The nested job 'test' is requesting 'id-token: write', but is only allowed 'id-token: none'.

ali-kafel
ali-kafel previously approved these changes Nov 4, 2025
@ali-kafel

Copy link
Copy Markdown
Member

🔒 Automated Update: The harden-runner configuration has been updated.

Changes:

  • Updated step-security/harden-runner to version v2.13.2
  • Updated egress-policy to block
  • Added policy: global-allowed-endpoints-policy
  • Added permissions: id-token: write to jobs using harden-runner (if not already present)

This change was applied automatically to workflow files in this PR.

@ali-kafel
ali-kafel merged commit d69708f into master Nov 5, 2025
5 checks passed
@ali-kafel
ali-kafel deleted the chore/GHA-041845-stepsecurity-remediation branch November 5, 2025 18:27
nexx88 pushed a commit that referenced this pull request Jul 1, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.2.0](v0.1.0...v0.2.0)
(2026-07-01)


### Features

* **v0.2.0:** security upgrade
([#26](#26))
([0c3f333](0c3f333))


### Miscellaneous Chores

* **ci:** bump GitHub Actions to Node 24
([#25](#25))
([75a9415](75a9415))
* **stepsecurity:** apply security best practices
([#20](#20))
([d69708f](d69708f))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants