CybercentreCanada/howler

Replace third-party github actions

Open

#39 opened on Jul 7, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (12 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (51 stars)
PR merge metrics
 (PR metrics pending)

Description

We currently use a number of third-party github actions that could lead to supply chain attacks. Removing these third-party dependencies eliminates that risk.

The current third party action list:

  • abatilo/actions-poetry@v4 - Poetry installation and configuration on buildhost
  • marocchino/sticky-pull-request-comment@v2 - Posting and updating sticky comments in pull requests (Not used when building packages/images, only PRs)
  • hoverkraft-tech/compose-action@v2.2.0 - used for handling docker compose initialization and cleanup

Contributor guide

Research direction
Identify the specific functionality of each third party action and determine the best way to replicate it using first party GitHub Actions or custom scripts.
Tech stack
pythongithub actions
Domain
securitydevops
Issue type
Security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70