The PMG GitHub Action installs PMG on a Linux GitHub Actions runner. PMG then wraps package manager commands such as npm install, pip install, or poetry add. The proxy blocks malicious packages before they run.

- uses: safedep/pmg@v1

Commit SHA pinning. The examples use the v1 tag for readability. Pin the action to a full commit SHA. This improves supply chain security. See the GitHub security hardening guide.

Out of the box the action gives:

• Malware blocking that uses the SafeDep real-time threat intelligence.
• A dependency cooldown. This blocks package versions published within the last 5 days.
• Proxy-based interception of supported package managers.

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 24
      - uses: safedep/pmg@v1
      - run: npm ci

Use the correct step order. Put safedep/pmg after setup-node or setup-python. Each of these steps prepends to PATH. PMG must put its shims in front of the real toolchain shims on PATH. Run pmg setup info --json. The user_shims.dir value shows the PMG shim directory.

This step order also works when releases change the shim location. Pre-v2 releases put shims in one directory. Newer releases put them under the XDG data directory. The action adds whichever directory the install creates.

Each toggle input defaults to empty. When an input is empty, the action sets no PMG_* environment variable. PMG then uses its own default for that key. This behavior prevents the action from silently overriding a YAML file loaded through config-file. Set an input to override the default.

- uses: safedep/pmg@v1
  with:
    api-key:   ${{ secrets.SAFEDEP_API_KEY }}
    tenant-id: ${{ secrets.SAFEDEP_TENANT_ID }}
- run: npm ci
# Flush events at the end of the job.
- run: pmg cloud sync --timeout 60s
  if: always()

Why the sync step? Composite actions have no clean post-step hook. A trailing step with if: always() keeps the upload visible in the workflow file.

The endpoint-id defaults to github-actions/${{ github.repository }}. Each workflow on the same repository appears as one endpoint in the SafeDep Cloud UI. Override it for per-environment splits:

- uses: safedep/pmg@v1
  with:
    api-key:     ${{ secrets.SAFEDEP_API_KEY }}
    tenant-id:   ${{ secrets.SAFEDEP_TENANT_ID }}
    endpoint-id: github-actions/${{ github.repository }}/prod

# .github/pmg.yml
paranoid: true
dependency_cooldown:
  enabled: true
  days: 14
trusted_packages:
  - purl: pkg:npm/@my-org/internal-pkg
    reason: "Internal package, signed by build pipeline"

- uses: safedep/pmg@v1
  with:
    config-file: .github/pmg.yml

The action copies the file to ~/.config/safedep/pmg/config.yml before pmg setup install runs. PMG merges any missing template keys into the file. Specify only the keys to override.

- uses: safedep/pmg@v1
  with:
    sandbox: true
    sandbox-driver: landlock   # or "bubblewrap"
- run: npm ci

The action runs systemctl stop apparmor and clears kernel.apparmor_restrict_unprivileged_userns. This lets unprivileged user namespaces work. The change modifies the runner. Enable it only when you need install-script containment.

You can override any PMG config key with a PMG_* environment variable. Set it on the job or on the install step:

- uses: safedep/pmg@v1
- run: npm ci
  env:
    PMG_DEPENDENCY_COOLDOWN_DAYS: 10

See docs/config.md for the full mapping.

Issue #248 tracks macOS and Windows runner support.