fix: set body decompress plugin as tested by azurit · Pull Request #56 · coreruleset/plugin-registry

azurit · 2026-10-21T08:09:03Z

Summary by CodeRabbit

Documentation
- Updated the body-decompress plugin’s registry status from “being tested” to “tested.”
- Synchronized the status across the project documentation and registry listings.
- The plugin now displays the tested-status indicator in published registry information.

coderabbitai · 2026-10-21T08:09:20Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Advanced
Run ID: fb33bf3a-1635-49d2-8d43-bcc57b1ab40f

📥 Commits

Reviewing files that changed from the base of the PR and between 5a872f5 and 5d88ec7.

📒 Files selected for processing: 3

README.md
registry.json
registry.yaml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The body-decompress plugin status changes from “being tested” to tested in the registry and README.

Changes: Body Decompress Status

Layer / File(s)	Summary
Update plugin status `registry.json`, `registry.yaml`, `README.md`	The registry files change the status to `tested`. The README displays the tested-status checkmark.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested labels: release:ignore

Merge Risk: ⚪ Minimal · up to 5d88e

The plugin status is updated consistently across the registry and README, with no merge-blocking risk identified.

Pre-merge checks: 16 · 1 · 1

Failed checks: 1 warning · 1 inconclusive

Check name	Status	Explanation	Resolution
Renovate: Config Present And Valid		No Renovate configuration exists in the PR head. The PR modifies root files, so this check applies. Check 1 fails because none of the four accepted Renovate config paths exists.	Add `renovate.json` or `renovate.json5` in the repository root, or the accepted `.github/` equivalent. Set `$schema` to `https://docs.renovatebot.com/renovate-schema.json` and include `github>coreruleset/renovate-config` in `extends`.
Ai Contribution Disclosure		The diff is a trivial three-line registry status update. It contains no generated code, tests, comments, or AI signatures, and the three commit messages contain no attribution trailers. The supplied c…	Provide the complete PR body. Verify `## what`, `## why`, and `## refs`; if `## ai disclosure` is present, verify concrete tool, assistance, and review details.

Passed checks: 16 passed

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: marking the body-decompress plugin as tested.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Regex Assembly Is The Source Of Truth		Passed: not applicable. The pull request changes only README.md, registry.json, and registry.yaml. It does not modify an `@rx` pattern in rules/*.conf or any file under regex-assembly/.
Rule Change Requires Go-Ftw Test Coverage		Not applicable. The pull request changes only plugin metadata in README.md, registry.json, and registry.yaml. It does not modify SecRule directives in rules/.conf or plugins/.conf, and it does not c…
Redos Risk & Re2 Compatibility		Not applicable. The pull request changes only `README.md`, `registry.json`, and `registry.yaml`. It does not add or modify `@rx` patterns, `regex-assembly/*.ra`, `regexp.MustCompile`, or Python `re.co…
False Positive Risk & Existing Coverage		Passed: not applicable. The PR changes only README.md, registry.json, and registry.yaml. It changes the body-decompress status from being-tested to tested. It does not add or widen a detection pattern…
Crs Rule Metadata & Id Conventions		Passed — not applicable. The pull request changes only README.md, registry.json, and registry.yaml. It does not add or modify a SecRule in rules/.conf, plugins/.conf, or crs-setup.conf.example.
Rule & Config Breaking Changes		PASS — The pull request changes only the body-decompress registry status from `being-tested` to `tested` in `registry.yaml`, `registry.json`, and the generated README table. It does not remove or renu…
Owasp Security (Web, Api & Llm)		PASS — The pull request changes only the `body-decompress` registry status from `being-tested` to `tested` in `registry.yaml`, `registry.json`, and the generated README table. The values are consisten…
Unpinned Dependencies & Actions		Passed. not applicable: the diff changes only README.md, registry.json, and registry.yaml. It changes no manifest, lockfile, Dockerfile, workflow, or pipeline file covered by this check.
Secrets, Payloads & Pii In Logs		The pull request changes only the `body-decompress` status from `being-tested` to `tested` in `registry.yaml`, `registry.json`, and the generated README table. It adds no logs, errors, telemetry, requ…
New Dependency Scrutiny		PASS: The pull request changes only the `body-decompress` status from `being-tested` to `tested` in `registry.yaml`, `registry.json`, and the generated README table. It adds no package manifest entry,…
Install & Build-Time Code Execution		The pull request changes only the body-decompress status from `being-tested` to `tested` in `registry.yaml`, `registry.json`, and the generated README table. It adds no installer, build step, workflow…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Full details: Rule Change Requires Go-Ftw Test Coverage

Explanation

Not applicable. The pull request changes only plugin metadata in README.md, registry.json, and registry.yaml. It does not modify SecRule directives in rules/.conf or plugins/.conf, and it does not change regex-assembly patterns.

Full details: Redos Risk & Re2 Compatibility

Explanation

Not applicable. The pull request changes only README.md, registry.json, and registry.yaml. It does not add or modify @rx patterns, regex-assembly/*.ra, regexp.MustCompile, or Python re.compile calls.

Full details: False Positive Risk & Existing Coverage

Explanation

Passed: not applicable. The PR changes only README.md, registry.json, and registry.yaml. It changes the body-decompress status from being-tested to tested. It does not add or widen a detection pattern or add a rule under rules/.conf, plugins/.conf, or regex-assembly/.

Full details: Rule & Config Breaking Changes

Explanation

PASS — The pull request changes only the body-decompress registry status from being-tested to tested in registry.yaml, registry.json, and the generated README table. It does not remove or renumber rule IDs, change CRS defaults, tags, messages, paranoia levels, data files, or tooling APIs. The repository documents status as a plugin maturity field, so this metadata update does not match an explicit breaking-change condition.

Full details: Owasp Security (Web, Api & Llm)

Explanation

PASS — The pull request changes only the body-decompress registry status from being-tested to tested in registry.yaml, registry.json, and the generated README table. The values are consistent and valid. This metadata change does not add authentication, authorization, input handling, dependencies, network behavior, secrets, or other affected behavior matching the OWASP failure conditions. The registry documentation also states that tested means integration tests exist and pass, not that the plugin is a security guarantee.

Full details: Secrets, Payloads & Pii In Logs

Explanation

The pull request changes only the body-decompress status from being-tested to tested in registry.yaml, registry.json, and the generated README table. It adds no logs, errors, telemetry, request data, credentials, payloads, or PII.

Full details: New Dependency Scrutiny

Explanation

PASS: The pull request changes only the body-decompress status from being-tested to tested in registry.yaml, registry.json, and the generated README table. It adds no package manifest entry, GitHub Action, or Buildkite plugin reference.

Full details: Install & Build-Time Code Execution

Explanation

The pull request changes only the body-decompress status from being-tested to tested in registry.yaml, registry.json, and the generated README table. It adds no installer, build step, workflow, shell script, package hook, Docker fetch, Go environment override, or Terraform provisioner covered by this check.

Full details: Ai Contribution Disclosure

Explanation

The diff is a trivial three-line registry status update. It contains no generated code, tests, comments, or AI signatures, and the three commit messages contain no attribution trailers. The supplied context does not include the actual PR body, so the required lowercase sections and any AI disclosure fields cannot be verified.

Resolution

Provide the complete PR body. Verify ## what, ## why, and ## refs; if ## ai disclosure is present, verify concrete tool, assistance, and review details.

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

EsadCetiner

Could you update the plugin.yaml file and add a badge to the read me? You can steal the badge code from one of the other plugins.

azurit · 2026-10-22T06:02:05Z

Could you update the plugin.yaml file and add a badge to the read me? You can steal the badge code from one of the other plugins.

Really don't know what you mean.

EsadCetiner · 2026-10-22T07:05:33Z

@azurit I mean within the body decompress repository

azurit · 2026-10-22T07:14:59Z

I don't see how this can be set in plugin.yaml.

EsadCetiner · 2026-10-22T07:17:04Z

https://github.com/coreruleset/body-decompress-plugin/blob/738f753802c2d5d76dafb773c74c13fb7da895f1/plugin.yaml#L17

Update that line to tested

EsadCetiner

Looks good, can you add a badge to the plugin's readme too?

azurit added 3 commits October 21, 2026 10:06

Update registry.yaml

7e76ce8

Update registry.json

b56c144

Update README.md

5d88ec7

coderabbitai Bot added the release:ignore label Oct 21, 2026

EsadCetiner reviewed Oct 21, 2026

View reviewed changes

EsadCetiner approved these changes Oct 22, 2026

View reviewed changes

azurit merged commit c10f563 into coreruleset:main Oct 22, 2026
3 checks passed

Navigation Menu

Repository navigation

fix: set body decompress plugin as tested - #56

fix: set body decompress plugin as tested#56
azurit merged 3 commits into
coreruleset:mainfrom
azurit:tested

azurit commented Oct 21, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Oct 21, 2026 •

edited

Loading

Uh oh!

EsadCetiner left a comment

Uh oh!

azurit commented Oct 22, 2026

Uh oh!

EsadCetiner commented Oct 22, 2026

Uh oh!

azurit commented Oct 22, 2026

Uh oh!

EsadCetiner commented Oct 22, 2026

Uh oh!

EsadCetiner left a comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

azurit commented Oct 21, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

EsadCetiner left a comment

Choose a reason for hiding this comment

Uh oh!

azurit commented Oct 22, 2026

Uh oh!

EsadCetiner commented Oct 22, 2026

Uh oh!

azurit commented Oct 22, 2026

Uh oh!

EsadCetiner commented Oct 22, 2026

Uh oh!

EsadCetiner left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

azurit commented Oct 21, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Oct 21, 2026 •

edited

Loading