github action

Every pull request, checked.

Periderm runs in your GitHub Actions and leaves one comment on each pull request. It updates the same comment on every push, so you always see where the branch stands.

Free on public repositories. No account needed.

periderm bot commented · edited just now
Periderm · 86/100 · Ready
✓ 142 checks passed | 2 warnings
  • · Missing Terms of Service
  • · Unbounded API retry on /api/ai

Set it up in two minutes

  1. 1. Create .github/workflows/periderm.yml in your repository:

    name: Periderm
    on:
      pull_request:
      push:
        branches: [main]
    
    permissions:
      contents: read
      pull-requests: write
    
    jobs:
      periderm:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v4
          - uses: Prince-Japheth/periderm-action@v1
            with:
              # Public repos: leave this out. Private repos: add a Team token as a repo secret.
              token: ${{ secrets.PERIDERM_TOKEN }}
    
  2. 2. Commit it to your default branch.
  3. 3. Open a pull request. Periderm comments within a minute or two.

Pricing

Public repos
Free
no account needed

Every check, one comment per PR, annotations and job summary.

Team
$29
per month

Private repositories, dashboard sync, everything in Unlimited.

Business
$99
per month

Everything in Team, plus the team dashboard and org-wide rules.

Questions

Is it really free for public repositories?
Yes. No account, no token, no limit. Add the workflow file and open a pull request.
What do private repositories need?
The Team plan ($29/month) or Business ($99/month, adds the team dashboard). Create a CI token in your dashboard and save it as the PERIDERM_TOKEN repository secret.
Does my code leave GitHub?
No. The scan runs inside your GitHub Actions job. With a token, only findings and scores are sent to your Periderm dashboard.
Will it spam my pull requests?
No. It posts one comment per pull request and edits that same comment on every push.
Can it block a merge?
Yes. By default the job fails when there's a critical finding. Set fail-on to high, medium or never to change that, then make the check required in your branch protection rules.