PyCharm Python Security Scanner workflow (msoedov/langcorn)

The PyCharm Python Security Scanner workflow from msoedov/langcorn, explained and optimized by Latchkey.

What it does

This is the PyCharm Python Security Scanner workflow from the msoedov/langcorn repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: PyCharm Python Security Scanner

on:
  schedule:
    - cron: "0 0 * * *"

jobs:
  security_checks:
    runs-on: ubuntu-latest
    name: Execute the pycharm-security action
    steps:
      - uses: actions/checkout@v1
      - name: PyCharm Python Security Scanner
        uses: tonybaloney/pycharm-security@1.19.0

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: PyCharm Python Security Scanner
 
on:
  schedule:
    - cron: "0 0 * * *"
 
jobs:
  security_checks:
    timeout-minutes: 30
    runs-on: latchkey-small
    name: Execute the pycharm-security action
    steps:
      - uses: actions/checkout@v1
      - name: PyCharm Python Security Scanner
        uses: tonybaloney/pycharm-security@1.19.0
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow