Adopt StepSecurity Harden Runner for GitHub Actions

Open
#26 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Review the GitHub Actions configurations and the referenced PRs for loopback/cicd and loopback/loopback.io, then compare the proposed adoption with StepSecurity Harden Runner's Ubuntu, sudo, and container-action limitations. Done means the applicable repositories use the action to audit the stated risks and the repository checklist reflects their status.

Written by the indexing model from the issue text.

Description

The StepSecurity Harden Runner GitHub Action contains a Go-based client which would audit and, if configured, restrict the following:

  • Of Interest:
    • Source code overwriting
    • Network activity
  • Others (not as relevant):
    • GitHub Action workflow permission
    • GitHub Action pinning

Limitations:

  • Ubuntu OS only
  • GitHub Actions only (No Travis CI or AppVeyor)
  • Does not work with container-based actions (Requires sudo privileges)

Although StepSecurity's Online Tool is referenced by the OpenSSF Scorecard Guide, the "Harden Runner" GitHub Action is not actually referenced or recommended. However, "Harden Runner" is used within the OpenSSF Scorecard GitHub Repository itself.

StepSecurity Harden Runner GitHub Repository: https://github.com/step-security/harden-runner

Loosely-related to https://github.com/loopbackio/security/issues/25 (Part of OpenSSF Scorecard check).

GitHub repositories

Dominant language
TypeScript
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/security

All issues in loopbackio/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.