KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #ai-agents #developer-tools #ai-agent #claude-code #mcp #typescript #codex #cli #rust #deepseek-harness

anti-slop

★ 763 Open GitHub ↗

A GitHub action that detects and automatically closes low-quality and AI slop PRs.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Anti Slop

A GitHub Action that detects and automatically closes low-quality and AI slop PRs. It ships with **34 check rules** covering PR branches, size, title, description, template, commit messages, file changes, user signals and contributor history.

Everything is configurable through **57 options** including checks, exemptions and failure actions, that you do not have to touch if you don't want to, as we've set sensible defaults.

> [!IMPORTANT]
> Anti Slop is currently **v0** and subject to breaking changes prior to v1.0.0. Pin to a specific version or commit SHA if you need stability.

## Why Anti Slop?

Open-source maintainers are drowning in low-quality and AI-generated slop PRs. These PRs undermine real contributions and waste reviewers time. Anti Slop stops these PRs before they reach your review queue.

- **Fast:** The entire action runs in under 15 seconds which means slop PRs are caught and closed before you even notice them.
- **Keep open source open:** The beauty of open source is that anyone can contribute. Anti Slop blocks low-quality and AI-generated PRs without forcing you to restrict contributions to Members only - new contributors are not penalized just for being new.
- **Language agnostic:** All checks are fully language agnostic and work with any programming language out of the box.
- **Battle-tested rules:** All 31 checks are derived from patterns identified across 130+ manually reviewed AI slop PRs submitted to different large open-source projects.
- **Thoughtful defaults:** Defaults are created and adjusted based on hands-on experience maintaining [Coolify](https://github.com/coollabsio/coolify) (50K+ stars, 120+ slop PRs per month).
- **Anti-slop, not anti-AI:** Genuinely good AI-assisted contributions are not penalized.
- **Configurable sensitivity:** The [`max-failures`](#max-failures) threshold controls how many checks must fail before any actions are taken. The higher the number, the less likely a legitimate contributor is flagged.
- **Zero-configuration exemptions:** Owners, Members and Collaborators are automatically exempt by default with zero configuration needed.
- **No inline scripts:** No ugly, unmaintainable and unreadable inline GitHub Action scripts. Just clean, well-named configuration options that are easy to understand and maintain.
- **Immutable releases:** Pin to a specific version (e.g. `v0.2.0`) and it is guaranteed immutable by GitHub - no convoluted SHA pinning needed but the same security benefits as if you pinned to a specific SHA.

## Quick Start

Add this workflow file `.github/workflows/pr-quality.yaml`:

```yaml
name: PR Quality

permissions:
  contents: read
  issues: read
  pull-requests: write

on:
  pull_request_target:
    types: [opened, reopened]

jobs:
  anti-slop:
    runs-on: ubuntu-latest
    steps:
      - uses: peakoss/anti-slop@v0
        with:
          max-failures: 4
```

## Recommended Permissions

For the execution of this action it must be able to read the contents of pull requests and issues to run checks.

In addition based on additionally configured options (eg. comment, add label, remove label, etc.) the action could require more permissions.

We recommend the following permissions by default:

```yaml
permissions:
  contents: read
  issues: read
  pull-requests: write
```

You can find more information about how to use permissions with GitHub Actions in the [GitHub Actions documentation](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#permissions).

## Full Example

Below is a full example workflow file with every option and its default value so you can much faster configure the action to your needs.

<details>
<summary>Full Example Workflow</summary>

```yaml
name: PR Quality

permissions:
  contents: read
  issues: read
  pull-requests: write

on:
  pull_request_target:
    types: [opened, reopened]

jobs:
  pr-quality:
    runs-on: ubuntu-latest
    steps:
      - uses: peakoss/anti-slop@v0
        with:
          # General Settings
          max-failures: 4

# PR Branch Checks
          allowed-target-branches: ""
          blocked-target-branches: ""
          allowed-source-branches: ""
          blocked-source-branches: |
            main
            master

# PR Size Checks
          max-changed-files: 50
          max-changed-lines: 10000

# PR Quality Checks
          max-negative-reactions: 0
          require-maintainer-can-modify: true

# PR Title Checks
          require-conventional-title: false

# PR Description Checks
          require-description: true
          max-description-length: 2500
          max-emoji-count: 2
          max-code-references: 5
          require-linked-issue: false
          blocked-terms: ""
          blocked-issue-numbers: ""

# PR Template Checks
          require-pr-template: false
          strict-pr-template-sections: ""
          optional-pr-template-sections: ""
          max-additional-pr-template-sections: 0

# Commit Message Checks
          max-commit-message-length: 500
          require-conventional-commits: false
          require-commit-author-match: true
          blocked-commit-authors: ""

# File Checks
          allowed-file-extensions: ""
          allowed-paths: ""
          blocked-paths: |
            README.md
            SECURITY.md
            LICENSE
            CODE_OF_CONDUCT.md
          require-final-newline: true
          max-added-comments: 10

# User Checks
          detect-spam-usernames: true
          min-account-age: 30
          max-daily-forks: 6
          require-public-profile: true
          min-profile-completeness: 4

# Merge Checks
          min-repo-merged-prs: 0
          min-repo-merge-ratio: 0
          min-global-merge-ratio: 30
          global-merge-ratio-exclude-own: false

# Exemptions
          exempt-draft-prs: false
          exempt-bots: |
            actions-user
            autofix-ci[bot]
            dependabot[bot]
            renovate[bot]
            github-actions[bot]
          exempt-users: ""
          exempt-author-association: "OWNER,MEMBER,COLLABORATOR"
          exempt-label: "exempt"
          exempt-pr-label: ""
          exempt-all-milestones: false
          exempt-all-pr-milestones: false
          exempt-milestones: ""
          exempt-pr-milestones: ""

# PR Success Actions
          success-add-pr-labels: ""

# PR Failure Actions
          failure-remove-pr-labels: ""
          failure-remove-all-pr-labels: false
          failure-add-pr-labels: ""
          failure-pr-message: ""
          close-pr: true
          lock-pr: false
```

</details>

## All Options

The only required input is `github-token` and it is automatically set to the workflow's `GITHUB_TOKEN` by its default value.

### Inputs

| Input                                                                         | Description                                                                                                                                                                                         | Default                                                                                      |
| ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| [`github-token`](#github-token)                                               | GitHub token used to authenticate API requests.                                                                                                                                                     | `${{ github.token }}`                                                                        |
| [`max-failures`](#max-failures)                                               | Number of check failures needed before failure actions are triggered.                                                                                                                               | `4`                                                                                          |
| [`allowed-target-branches`](#allowed-target-branches)                         | Newline-separated target branch patterns to allow. Empty allows all branches.                                                                                                                       | `""`                                                                                         |
| [`blocked-target-branches`](#blocked-target-branches)                         | Newline-separated target branch patterns to block.                                                                                                                                                  | `""`                                                                                         |
| [`allowed-source-branches`](#allowed-source-branches)                         | Newline-separated source branch patterns to allow. Empty allows all branches.                                                                                                                       | `""`                                                                                         |
| [`blocked-source-branches`](#blocked-source-branches)                         | Newline-separated source branch patterns to block.                                                                                                                                                  | `main`, `master`                                                                             |
| [`max-changed-files`](#max-changed-files)                                     | Maximum number of changed files allowed in the PR. 0 disables this check.                                                                                                                           | `50`                                                                                         |
| [`max-changed-lines`](#max-changed-lines)                                     | Maximum number of changed lines (additions + deletions) allowed in the PR. 0 disables this check.                                                                                                   | `10000`                                                                                      |
| [`max-negative-reactions`](#max-negative-reactions)                           | Maximum number of negative reactions (thumbs down + confused) allowed on the PR. 0 disables this check.                                                                                             | `0`                                                                                          |
| [`require-maintainer-can-modify`](#require-maintainer-can-modify)             | Require the PR to allow maintainers to push to the source branch.                                                                                                                                   | `true`                                                                                       |
| [`require-conventional-title`](#require-conventional-title)                   | Require PR titles to follow Conventional Commits format (e.g. 'feat:', 'fix:', 'feat(scope):').                                                                                                     | `false`                                                                                      |
| [`require-description`](#require-description)                                 | Require a non-empty PR description.                                                                                                                                                                 | `true`                                                                                       |
| [`max-description-length`](#max-description-length)                           | Maximum character length for the PR description. 0 disables this check.                                                                                                                             | `2500`                                                                                       |
| [`max-emoji-count`](#max-emoji-count)                                         | Maximum number of emojis allowed in the PR title and description. 0 disables this check.                                                                                                            | `2`                                                                                          |
| [`max-code-references`](#max-code-references)                                 | Maximum number of code references (file paths, function/method calls) allowed in the PR description. 0 disables this check.                                                                         | `5`                                                                                          |
| [`require-linked-issue`](#require-linked-issue)                               | Require the PR to reference at least one issue in the PR description.                                                                                                                               | `false`                                                                                      |
| [`blocked-terms`](#blocked-terms)                                             | Newline-separated list of terms blocked from appearing in the PR description.                                                                                                                       | `""`                                                                                         |
| [`blocked-issue-numbers`](#blocked-issue-numbers)                             | Comma-separated list of issue numbers blocked from being referenced in the PR description.                                                                                                          | `""`                                                                                         |
| [`require-pr-template`](#require-pr-template)                                 | Require the PR description to follow the repository PR template structure.                                                                                                                          | `false`                                                                                      |
| [`strict-pr-template-sections`](#strict-pr-template-sections)                 | Comma-separated PR template section headings (without '#') classified as strict. All checkboxes must be present and checked. Only applies when require-pr-template is enabled.                      | `""`                                                                                         |
| [`optional-pr-template-sections`](#optional-pr-template-sections)             | Comma-separated PR template section headings (without '#') classified as optional. Can be removed from the description without failing the check. Only applies when require-pr-template is enabled. | `""`                                                                                         |
| [`max-additional-pr-template-sections`](#max-additional-pr-template-sections) | Maximum number of additional sections not in the template that are allowed in the PR description. 0 disables this check.                                                                            | `0`                                                                                          |
| [`max-commit-message-length`](#max-commit-message-length)                     | Maximum character length for individual commit messages. 0 disables this check.                                                                                                                     | `500`                                                                                        |
| [`require-conventional-commits`](#require-conventional-commits)               | Require all commit messages to follow Conventional Commits format (e.g. 'feat:', 'fix:', 'feat(scope):').                                                                                           | `false`                                                                                      |
| [`require-commit-author-match`](#require-commit-author-match)                 | Require every commit in the PR to be authored by the same GitHub user who opened the PR.                                                                                                            | `true`                                                                                       |
| [`blocked-commit-authors`](#blocked-commit-authors)                           | Comma-separated list of blocked commit author usernames.                                                                                                                                            | `""`                                                                                         |
| [`allowed-file-extensions`](#allowed-file-extensions)                         | Comma-separated list of allowed file extensions (e.g. '.ts,.js') for changed files. Empty allows all.                                                                                               | `""`                                                                                         |
| [`allowed-paths`](#allowed-paths)                                             | Newline-separated file or folder paths to allow for changed files. Entries ending with '/' match folders. Empty allows all.                                                                         | `""`                                                                                         |
| [`blocked-paths`](#blocked-paths)                                             | Newline-separated file or folder paths to block for changed files. Entries ending with '/' match folders.                                                                                           | `README.md`, `SECURITY.md`, `LICENSE`, `CODE_OF_CONDUCT.md`                                  |
| [`require-final-newline`](#require-final-newline)                             | Require all changed files to end with a newline character.                                                                                                                                          | `true`                                                                                       |
| [`max-added-comments`](#max-added-comments)                                   | Maximum number of added comments in all changed files. 0 disables this check.                                                                                                                       | `10`                                                                                         |
| [`detect-spam-usernames`](#detect-spam-usernames)                             | Detect usernames that match common spam patterns.                                                                                                                                                   | `true`                                                                                       |
| [`min-account-age`](#min-account-age)                                         | Minimum GitHub account age in days. 0 disables this check.                                                                                                                                          | `30`                                                                                         |
| [`max-daily-forks`](#max-daily-forks)                                         | Maximum number of repositories forked by the user in any 24-hour window. 0 disables this check.                                                                                                     | `6`                                                                                          |
| [`require-public-profile`](#require-public-profile)                           | Require the PR author to have a public GitHub profile.                                                                                                                                              | `true`                                                                                       |
| [`min-profile-completeness`](#min-profile-completeness)                       | Minimum number of profile signals (name, email, bio, etc.) the user must have to pass. 0 disables this check.                                                                                       | `4`                                                                                          |
| [`min-repo-merged-prs`](#min-repo-merged-prs)                                 | Minimum number of merged PRs in this repository from the author. 0 disables this check.                                                                                                             | `0`                                                                                          |
| [`min-repo-merge-ratio`](#min-repo-merge-ratio)                               | Minimum merge/close PR ratio percentage in this repository. 0 disables this check.                                                                                                                  | `0`                                                                                          |
| [`min-global-merge-ratio`](#min-global-merge-ratio)                           | Minimum merge/close PR ratio percentage across all repositories. 0 disables this check.                                                                                                             | `30`                                                                                         |
| [`global-merge-ratio-exclude-own`](#global-merge-ratio-exclude-own)           | Exclude PRs to the author's own repositories from the global merge ratio calculation.                                                                                                               | `false`                                                                                      |
| [`exempt-draft-prs`](#exempt-draft-prs)                                       | Exempt draft PRs from all checks.                                                                                                                                                                   | `false`                                                                                      |
| [`exempt-bots`](#exempt-bots)                                                 | Newline-separated list of bot usernames exempt from all checks.                                                                                                                                     | `actions-user`, `autofix-ci[bot]`, `dependabot[bot]`, `renovate[bot]`, `github-actions[bot]` |
| [`exempt-users`](#exempt-users)                                               | Comma-separated list of GitHub usernames exempt from all checks.                                                                                                                                    | `""`                                                                                         |
| [`exempt-author-association`](#exempt-author-association)                     | Comma-separated list of GitHub author associations exempt from all checks.                                                                                                                          | `OWNER,MEMBER,COLLABORATOR`                                                                  |
| [`exempt-label`](#exempt-label)                                               | Label name that exempts PRs and Issues from all checks when it is present.                                                                                                                          | `exempt`                                                                                     |
| [`exempt-pr-label`](#exempt-pr-label)                                         | Label name that exempts PRs from all checks when it is present.                                                                                                                                     | `""`                                                                                         |
| [`exempt-all-milestones`](#exempt-all-milestones)                             | Exempt all PRs and Issues that are assigned to any milestone.                                                                                                                                       | `false`                                                                                      |
| [`exempt-all-pr-milestones`](#exempt-all-pr-milestones)                       | Exempt all PRs that are assigned to any milestone.                                                                                                                                                  | `false`                                                                                      |
| [`exempt-milestones`](#exempt-milestones)                                     | Comma-separated list of milestone titles. PRs and Issues assigned to any listed milestone are exempt.                                                                                               | `""`                                                                                         |
| [`exempt-pr-milestones`](#exempt-pr-milestones)                               | Comma-separated list of milestone titles. PRs assigned to any listed milestone are exempt.                                                                                                          | `""`                                                                                         |
| [`success-add-pr-labels`](#success-add-pr-labels)                             | Comma-separated list of labels to add to the PR on success.                                                                                                                                         | `""`                                                                                         |
| [`failure-remove-pr-labels`](#failure-remove-pr-labels)                       | Comma-separated list of labels to remove from the PR on failure.                                                                                                                                    | `""`                                                                                         |
| [`failure-remove-all-pr-labels`](#failure-remove-all-pr-labels)               | Remove all labels from the PR on failure.                                                                                                                                                           | `false`                                                                                      |
| [`failure-add-pr-labels`](#failure-add-pr-labels)                             | Comma-separated list of labels to add to the PR on failure.                                                                                                                                         | `""`                                                                                         |
| [`failure-pr-message`](#failure-pr-message)                                   | Comment posted on the PR when the maximum number of failures is reached. Empty posts no comment.                                                                                                    | `""`                                                                                         |
| [`close-pr`](#close-pr)                                                       | Close the PR when the maximum number of failures is reached.                                                                                                                                        | `true`                                                                                       |
| [`lock-pr`](#lock-pr)                                                         | Lock the PR conversation after closing.                                                                                                                                                             | `false`                                                                                      |

### Outputs

| Output          | Description                                      |
| --------------- | ------------------------------------------------ |
| `total-checks`  | Total number of checks that were run.            |
| `failed-checks` | Number of checks that failed.                    |
| `passed-checks` | Number of checks that passed.                    |
| `result`        | Overall result: `passed`, `failed` or `skipped`. |

## Details

### github-token

GitHub token used to authenticate API requests. This is automatically provided by the workflow run via `${{ github.token }}` and inherits the permissions defined in the workflow's [`permissions`](#recommended-permissions) block.

Default: `${{ github.token }}`

### max-failures

The number of individual check failures required before failure actions (close, lock, comment, etc.) are triggered.

This is the primary knob for controlling false positives. A higher value means more checks must fail before the PR is acted upon, making it less likely that a legitimate contribution is mistakenly closed. A lower value is more aggressive and catches slop easier but increases the risk of false positives.

- Set to `1` for zero tolerance -> any single check failure triggers actions.
- Set to `4` (the default) for a balanced approach -> the PR must fail four separate checks before it is closed.

Valid range: `1` to `25`

Default: `4`

### allowed-target-branches

Newline-separated list of target branch patterns that the PR is allowed to target. If this list is non-empty, any PR targeting a branch that does not match at least one pattern will fail the `allowed-target-branches` check.

If left empty (the default), all target branches are allowed unless they match [`blocked-target-branches`](#blocked-target-branches).

If the same branch pattern appears in both `allowed-target-branches` and `blocked-target-branches`, **the blocked list takes precedence** and the branch will always be blocked.

See [Branch Pattern Matching](#branch-pattern-matching) for supported wildcard syntax.

Default: `""` (all branches allowed)

### blocked-target-branches

Newline-separated list of target branch patterns to block. Any PR targeting a branch that matches one of these patterns will fail the `blocked-target-branches` check.

If the same branch pattern appears in both [`allowed-target-branches`](#allowed-target-branches) and `blocked-target-branches`, **the blocked list takes precedence** and the branch will always be blocked.

See [Branch Pattern Matching](#branch-pattern-matching) for supported wildcard syntax.

Default: `""` (no branches blocked)

### allowed-source-branches

Newline-separated list of source (head) branch patterns that the PR is allowed to originate from. If this list is non-empty, any PR from a branch that does not match at least one pattern will fail the `allowed-source-branches` check.

If left empty (the default), all source branches are allowed unless they match [`blocked-source-branches`](#blocked-source-branches).

If the same branch pattern appears in both `allowed-source-branches` and `blocked-source-branches`, **the blocked list takes precedence** and the branch will always be blocked.

See [Branch Pattern Matching](#branch-pattern-matching) for supported wildcard syntax.

Default: `""` (all branches allowed)

### blocked-source-branches

Newline-separated list of source branch patterns to block. Any PR originating from a branch that matches one of these patterns will fail the `blocked-source-branches` check.

By default, PRs from `main` and `master` are blocked because slop PRs commonly push directly to the default branch and open a PR from there, rather than creating a feature branch. Also, using a default branch as a source branch can cause issues with workflows that are triggered by push events on forks.

If the same branch pattern appears in both [`allowed-source-branches`](#allowed-source-branches) and `blocked-source-branches`, **the blocked list takes precedence** and the branch will always be blocked.

See [Branch Pattern Matching](#branch-pattern-matching) for supported wildcard syntax.

Default: `main`, `master`

### max-changed-files

Maximum number of changed files allowed in the PR. If the PR contains more changed files than this limit, the `max-changed-files` check fails.

Set to `0` to disable this check entirely.

Valid range: `0` to `500`

Default: `50`

### max-changed-lines

Maximum number of changed lines (additions + deletions) allowed in the PR. If the PR contains more changed lines than this limit, the `max-changed-lines` check fails.

Set to `0` to disable this check entirely.

Valid range: `0` to `100000`

Default: `10000`

### max-negative-reactions

Maximum number of negative reactions (thumbs down and confused reactions) allowed on the PR. If the count exceeds this threshold, the `max-negative-reactions` check fails.

Set to `0` to disable this check entirely.

This can be useful as a community-driven signal: if multiple people have reacted negatively to a PR, it may indicate low quality or AI-generated content.

Valid range: `0` to `200`

Default: `0` (disabled)

### require-maintainer-can-modify

Require the PR to have the `Allow edits and access to secrets by maintainers` option enabled. When a PR author disables this, it prevents maintainers from pushing fixes to the PR branch.

Default: `true`

### require-conventional-title

Require PR titles to follow the [Conventional Commits](https://www.conventionalcommits.org/) format (e.g. `feat:`, `fix:`, `feat(scope):`, `chore!:`).

Default: `false`

### require-description

Require a non-empty PR description. PRs with a blank or whitespace-only description will fail the `require-description` check.

Default: `true`

### max-description-length

Maximum character length for the PR description. If the description exceeds this length, the `max-description-length` check fails.

Set to `0` to disable this check entirely.

Excessively long descriptions are often a sign of AI-generated content.

Valid range: `0` to `50000`

Default: `2500`

### max-emoji-count

Maximum number of emojis allowed in the PR title and description combined. If the count exceeds this threshold, the `max-emoji-count` check fails.

Set to `0` to disable this check entirely.

AI-generated PR descriptions tend to include excessive emojis.

Valid range: `0` to `30`

Default: `2`

### max-code-references

Maximum number of code references (file paths, function/method calls) allowed in the PR description. If the count exceeds this threshold, the `max-code-references` check fails.

Set to `0` to disable this check entirely.

AI-generated PR descriptions often include excessive inline code references to appear thorough.

Valid range: `0` to `40`

Default: `5`

### require-linked-issue

Require the PR to reference at least one issue in the PR description.

Default: `false`

### blocked-terms

Newline-separated list of terms that are blocked from appearing in the PR description. If any of these terms are found, the `blocked-terms` check fails. The match is case sensitive.

This can be very useful by creating a honeypot for AI. See more in the [honeypot trap section](#honeypot-traps).

Default: `""` (no terms blocked)

### blocked-issue-numbers

Comma-separated list of issue numbers that are blocked from being referenced. If the PR description references any of these issue numbers, the `blocked-issue-numbers` check fails.

This can be useful when creating a honeypot for AI. See more in the [honeypot trap section](#honeypot-traps).

Default: `""` (no issue numbers blocked)

### require-pr-template

Require the PR description to match the repository's PR template. When enabled, the action fetches the PR template from the repository (`.github/pull_request_template.md` or similar) and checks that the PR description contains its content structure.

For non-strict sections that contain more than one checkbox in the template, at least one checkbox must still be present and exactly one must be checked (radio-button semantics). Strict sections enforce stricter rules via [`strict-pr-template-sections`](#strict-pr-template-sections).

This is particularly effective against AI tools that generate their own description and PRs created via the API.

Default: `false`

### strict-pr-template-sections

Comma-separated list of PR template section headings (without the `#` prefix) classified as strict. If there are checkboxes in strict sections, all checkboxes must be present and checked. If any strict section fails validation, the `strict-pr-template-sections` check fails independently of the `pr-template` check.

This only applies when [`require-pr-template`](#require-pr-template) is enabled.

Default: `""` (no strict sections)

### optional-pr-template-sections

Comma-separated list of PR template section headings (without the `#` prefix) classified as optional. Optional sections can be entirely removed from the PR description without failing the check.

This is a configuration option for [`require-pr-template`](#require-pr-template) and only applies when that check is enabled.

Default: `""` (no optional sections)

### max-additional-pr-template-sections

Maximum number of additional sections not in the template that are allowed in the PR description. If the PR contains more extra sections than this limit, the check fails.

Set to `0` to disable this check entirely.

This is a configuration option for [`require-pr-template`](#require-pr-template) and only applies when that check is enabled.

Valid range: `0` to `20`

Default: `0` (disabled)

### max-commit-message-length

Maximum character length for individual commit messages. If any commit message exceeds this length, the `max-commit-message-length` check fails.

Set to `0` to disable this check entirely.

AI-generated commits often have excessively long or verbose commit messages.

Valid range: `0` to `5000`

Default: `500`

### require-conventional-commits

Require all commit messages in the PR to follow the [Conventional Commits](https://www.conventionalcommits.org/) format.

Default: `false`

### require-commit-author-match

Require every commit in the PR to be authored by the same GitHub user who opened the PR. If any commit has a different author, the `require-commit-author-match` check fails.

This helps catch PRs where commits were cherry-picked or copied from other contributors.

Default: `true`

### blocked-commit-authors

Comma-separated list of blocked commit author usernames. If any commit in the PR was authored by a username in this list, the `blocked-commit-authors` check fails.

This can be useful to block commits from known spam or bot accounts that are not covered by the exemption settings.

Default: `""` (no authors blocked)

### allowed-file-extensions

Comma-separated list of allowed file extensions (e.g. `.ts,.js,.json`). If any changed file has an extension not in this list, the `allowed-file-extensions` check fails.

Dotfiles (e.g. `.gitignore`) and extensionless files (e.g. `Makefile`) are exempt from this check.

If left empty (the default), all file extensions are allowed.

This can be very useful to quickly filter out slop PRs to add python code to a PHP project for example.

Default: `""` (all extensions allowed)

### allowed-paths

Newline-separated list of file or folder paths to allow for changed files. Entries ending with `/` match entire folders. If this list is non-empty, any changed file that does not match at least one entry will fail the `allowed-paths` check.

If left empty (the default), all paths are allowed unless they match [`blocked-paths`](#blocked-paths).

If the same path appears in both `allowed-paths` and [`blocked-paths`](#blocked-paths), **the blocked list takes precedence** and changes to that path will always be blocked.

Default: `""` (all paths allowed)

### blocked-paths

Newline-separated list of file or folder paths to block for changed files. Entries ending with `/` match entire folders. If any changed file matches one of these entries, the `blocked-paths` check fails.

The default blocks common repository metadata files that are frequent targets for slop PRs - trivial edits to README, LICENSE, SECURITY, or CODE_OF_CONDUCT files are a classic pattern.

If the same path appears in both [`allowed-paths`](#allowed-paths) and `blocked-paths`, **the blocked list takes precedence** and changes to that path will always be blocked.

Default: `README.md`, `SECURITY.md`, `LICENSE`, `CODE_OF_CONDUCT.md`

### require-final-newline

Require all changed files to end with a newline character. Files that do not end with a newline fail the `require-final-newline` check.

Default: `true`

### max-added-comments

Maximum number of added comments in all changed files. If the total number of added comment lines across all changed files exceeds this threshold, the `max-added-comments` check fails.

Set to `0` to disable this check entirely.

AI-generated code tends to add excessive comments explaining obvious logic.

Valid range: `0` to `500`

Default: `10`

### detect-spam-usernames

Detect usernames that match spam patterns. Usernames that are all digits, contain 2 or more consecutive digits, or contain an `ai` segment are flagged.

Default: `true`

### min-account-age

Minimum GitHub account age in days. If the PR author's account is newer than this many days, the `min-account-age` check fails.

Set to `0` to disable this check entirely.

Freshly created accounts are often throwaway accounts used for automated PR campaigns. The default of `30` days catches the most obvious cases. Increasing this to `60` or `90` provides stronger protection but may affect legitimate new GitHub users.

Valid range: `0` to `190` (days)

Default: `30`

### max-daily-forks

Maximum number of repositories forked by the user in any 24-hour sliding window. If the user exceeds this count, the `max-daily-forks` check fails.

Set to `0` to disable this check entirely.

Mass-forking is a common pattern for automated PR spam campaigns. A burst of forks in a short time window is a strong signal that the account is running automated tooling.

Valid range: `0` to `50`

Default: `6`

### require-public-profile

Require the PR author to have a public GitHub profile. If the author's profile is not public, the `require-public-profile` check fails.

Default: `true`

### min-profile-completeness

Minimum number of profile signals (out of 10) the user must have to pass. The check evaluates the following 10 signals: name, company, blog, location, email, hireable, bio, twitter, followers and following. If the user has fewer signals present than the configured minimum, the `min-profile-completeness` check fails.

Set to `0` to disable this check entirely.

Spam and AI-driven accounts tend to have minimal or empty profiles. Requiring a baseline level of profile completeness is an effective heuristic for filtering out throwaway accounts.

Valid range: `0` to `10`

Default: `4`

### min-repo-merged-prs

Minimum previously merged PRs in this repository required from the PR author. If the author has fewer than this many merged PRs, the `min-repo-merged-prs` check fails.

Set to `0` to disable this check entirely.

Setting this to `1` effectively gates your repository to only accept PRs from people who have previously had work merged.

Valid range: `0` to `20`

Default: `0` (disabled)

### min-repo-merge-ratio

Minimum merge/close PR ratio percentage in this repository. If the author's ratio of merged PRs to total closed PRs in this repo falls below this threshold, the `min-repo-merge-ratio` check fails.

Set to `0` to disable this check entirely.

A low merge ratio means the author has had many PRs closed without being merged in your repo, which is a strong signal of mostly low-quality contributions.

Valid range: `0` to `100` (percentage)

Default: `0` (disabled)

### min-global-merge-ratio

Minimum merge/close PR ratio percentage across all public GitHub repositories. If the author's global ratio of merged PRs to total closed PRs falls below this threshold, the `min-global-merge-ratio` check fails.

Set to `0` to disable this check entirely.

This is one of the most effective contributor health checks. An author who has a low global merge ratio has a history of submitting PRs that get rejected across many projects which is a very strong indicator of low-quality contributions.

The default of `30` means that at least 30% of the author's closed PRs across all repositories must have been merged. Use [`global-merge-ratio-exclude-own`](#global-merge-ratio-exclude-own) to exclude self-merged PRs from this calculation as that could skew the results.

Valid range: `0` to `100` (percentage)

Default: `30`

### global-merge-ratio-exclude-own

> [!Warning]
> Many maintainers maintain legitimate projects under their own repos and merge their own PRs on these projects, so this is set to `false` by default.

When set to `true`, PRs submitted to repositories owned by the PR author are excluded from the [`min-global-merge-ratio`](#min-global-merge-ratio) calculation.

This is useful because some users have a high merge ratio only because they merge their own PRs in their own repositories. Excluding self-owned repos gives a more accurate picture of how their contributions are received by other projects.

Default: `false`

### exempt-draft-prs

When set to `true`, draft PRs are exempt from all checks and skip processing entirely.

This can be useful if contributors use draft PRs as work-in-progress and you only want to run checks when the PR is marked as ready for review.

Default: `false`

### exempt-bots

Newline-separated list of bot usernames that are exempt from all checks. PRs from any of these bot accounts skip all checks entirely.

Default: `actions-user`, `autofix-ci[bot]`, `dependabot[bot]`, `renovate[bot]`, `github-actions[bot]`

### exempt-users

Comma-separated list of GitHub usernames that are exempt from all checks. PRs from any of these users skip all checks entirely.

Default: `""` (no users exempted)

### exempt-author-association

Comma-separated list of GitHub author associations to exempt from all checks. PRs from authors with any of these associations skip all checks entirely.

The default exempts `OWNER`, `MEMBER` and `COLLABORATOR` author associations which are people who are already trusted and have access to the repository (can also be read only). As you already trust these people they should not be flagged as low-quality contributions in any case.

Valid values: `OWNER`, `MEMBER`, `COLLABORATOR`, `CONTRIBUTOR`, `FIRST_TIMER`, `FIRST_TIME_CONTRIBUTOR`, `MANNEQUIN`, `NONE`

Default: `OWNER,MEMBER,COLLABORATOR`

### exempt-label

Name of a label that exempts PRs and Issues from all checks when it is present. If a PR has this label, all checks are skipped. This provides an escape hatch for maintainers to manually override the checks for specific PRs or PRs that just got reopened.

Default: `exempt`

### exempt-pr-label

Label name that exempts PRs from all checks when it is present. Works the same as [`exempt-label`](#exempt-label) but overrides the exempt label specifically for PRs.

If both `exempt-label` and `exempt-pr-label` are set, `exempt-pr-label` takes precedence.

Default: `""` (disabled)

### exempt-all-milestones

When set to `true`, all PRs and Issues that are assigned to any milestone are exempt from all checks.

Default: `false`

### exempt-all-pr-milestones

When set to `true`, all PRs that are assigned to any milestone are exempt from all checks. Overrides [`exempt-all-milestones`](#exempt-all-milestones) specifically for PRs.

Default: `false`

### exempt-milestones

Comma-separated list of milestone titles to exempt from all checks. PRs and Issues assigned to any of these milestones are exempt from all checks.

Default: `""` (no milestones exempt)

### exempt-pr-milestones

Comma-separated list of milestone titles to exempt from all checks. PRs assigned to any of these milestones are exempt from all checks. This overrides [`exempt-milestones`](#exempt-milestones) specifically for PRs.

If both `exempt-milestones` and `exempt-pr-milestones` are set, `exempt-pr-milestones` takes precedence.

Default: `""` (no milestones exempt)

### success-add-pr-labels

Comma-separated list of labels to add to the PR when all checks pass or the number of failures is below [`max-failures`](#max-failures).

Useful for quickly scanning open PRs that have been checked and verified by the action.

Default: `""` (no labels added)

Required permission: `pull-requests: write`

### failure-remove-pr-labels

Comma-separated list of labels to remove from the PR when the maximum number of failures is reached.

Default: `""` (no labels removed)

Required permission: `pull-requests: write`

### failure-remove-all-pr-labels

When set to `true`, all labels are removed from the PR when the maximum number of failures is reached.

Default: `false`

Required permission: `pull-requests: write`

### failure-add-pr-labels

Comma-separated list of labels to add to the PR when the maximum number of failures is reached.

Default: `""` (no labels added)

Required permission: `pull-requests: write`

### failure-pr-message

Comment posted on the PR when the maximum number of failures is reached. If left empty, no comment is posted. You can use this to explain to the PR author why their PR was closed or why it was flagged with a specific label if [`close-pr`](#close-pr) is disabled.

Default: `""` (no comment posted)

Required permission: `pull-requests: write`

### close-pr

When set to `true`, the PR is closed when the maximum number of failures is reached. Set this to `false` if you just want to comment or add a label to the PR on failure.

Default: `true`

Required permission: `pull-requests: write`

### lock-pr

When set to `true`, the PR conversation is locked after closing. This prevents further comments on the PR.

Default: `false`

Required permission: `pull-requests: write`

## Advanced Configuration

### Branch Pattern Matching

Branch patterns use the same glob pattern syntax as GitHub Actions.

- `*` matches any sequence of characters except `/`
- `**` matches any sequence of characters including `/`.

For example, `feature/*` matches `feature/login` but not `feature/deep/nested`, while `feature/**` matches both.

### Honeypot Traps

Blocked terms and blocked issue numbers act as invisible traps that many AI agents still fall for.

### Blocked Terms

1. Place a hidden instruction inside a markdown comment in your PR template `.github/pull_request_template.md` that tell an AI to include a specific word. Human contributors won't see these keywords (markdown comments are invisible in rendered markdown) but AI agents that read the raw template source could follow the instruction and expose themselves.

```markdown

```

2. Configure the action with the blocked term:

```yaml
blocked-terms: "PINEAPPLE"
```

### Blocked Issue Numbers

Blocking specific issues can be useful when some issues are limited to the core team only or when relying on a monetary bounty system on specific issues.

```yaml
blocked-issue-numbers: "123"
```

## Debugging

To see the debug logging from this action, you must set the secret `ACTIONS_STEP_DEBUG` to `true` in your repository.

## Star History

[![Star History Chart](https://api.star-history.com/svg?repos=peakoss/anti-slop&type=date&legend=top-left)](https://www.star-history.com/#peakoss/anti-slop&type=date&legend=top-left)

anti-slop

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README