fix: set antivirus plugin as 'tested'

[azurit]

Summary by CodeRabbit

• Documentation
  • Updated the antivirus plugin’s status from “being tested” to “tested” in the project information and plugin registry.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

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: 7b982a81-cb84-41b4-aaf8-3bd0b4fdd8b8

📥 Commits

Reviewing files that changed from the base of the PR and between 655ac2b and 3047831.

📒 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:

• coreruleset/coreruleset (manual)
• coreruleset/go-ftw (manual)
• coreruleset/crs-toolchain (manual)
• coreruleset/crs-linter (manual)
• coreruleset/documentation (manual)

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

Walkthrough

The antivirus plugin status changes from being tested to tested in registry.json, registry.yaml, and README.md. The README displays the tested status with a checkmark.

Changes

Antivirus plugin status

Layer / File(s)	Summary
Update antivirus status registry.json, registry.yaml, README.md	The registry files change the antivirus plugin status to tested. The README shows the tested status with a checkmark.

Priority: ⬇️ Low

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

Change: Other

Suggested labels: release:ignore, :jigsaw: plugin

Merge Risk: ⚪ Minimal · up to 30478

The antivirus status is updated consistently across the catalog and README. No actionable merge-blocking risk is established; merge after normal checks.

Architecture Summary

Architecture risk: 🔵 Low · up to 30478

The change affects 3 systems.

Changed systems: README.md, registry.json, registry.yaml

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — README.md (service) was modified; 1 changed file maps to changed impact.
• observed — registry.json (service) was modified; 1 changed file maps to changed impact.
• observed — registry.yaml (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in README.md: The antivirus plugin’s registry status changes from being tested to tested with a checkmark.
• observed — Modified behavior in registry.json: The antivirus plugin status changed from being-tested to tested.
• observed — Modified behavior in registry.yaml: The antivirus plugin’s status changed from being-tested to tested.

🚥 Pre-merge checks | ✅ 16 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Ai Contribution Disclosure	⚠️ Warning	The PR body contains only a CodeRabbit-generated summary. It lacks the required lowercase ## what, ## why, and ## refs sections. It also contains the prohibited AI-tool signature text `coderabbi…	Replace the PR body with concrete ## what, ## why, and ## refs sections. Add ## ai disclosure with the required concrete tool/version, assistance, and review fields if AI materially assisted. Remove the CodeRabbit-generated comment,…
Renovate: Config Present And Valid	⚠️ Warning	Renovate configuration check fails. The PR changes root files (README.md, registry.json, and registry.yaml), so the check triggers. The PR head contains none of the accepted files: `renovate.jso…	Add renovate.json at the repository root. Set $schema to https://docs.renovatebot.com/renovate-schema.json and include github>coreruleset/renovate-config in the extends array.

✅ Passed checks (16 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the antivirus plugin status to tested.
Docstring Coverage	✅ Passed	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	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Regex Assembly Is The Source Of Truth	✅ Passed	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	✅ Passed	Passed: not applicable. The PR changes only README.md, registry.json, and registry.yaml. It does not add or modify a SecRule in rules/.conf or plugins/.conf, and it does not change regex-assembly pa…
Redos Risk & Re2 Compatibility	✅ Passed	Not applicable. The pull request changes only README.md, registry.json, and registry.yaml. The diff does not add or modify a regular expression in rules/.conf, regex-assembly/.ra, or tooling code co…
False Positive Risk & Existing Coverage	✅ Passed	Passed: not applicable. The pull request changes only the antivirus status from being-tested to tested in README.md, registry.json, and registry.yaml. It does not add or widen a detection pa…
Crs Rule Metadata & Id Conventions	✅ Passed	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	✅ Passed	PASS — The pull request changes only the antivirus plugin status from being-tested to tested in registry.yaml, registry.json, and the generated README table. It does not remove or renumber rul…
Owasp Security (Web, Api & Llm)	✅ Passed	PASS — The pull request changes only the antivirus plugin status from being-tested to tested in registry.yaml, its generated registry.json, and the README table. The head JSON is valid, and al…
Unpinned Dependencies & Actions	✅ Passed	Passed: not applicable. The pull request changes only README.md, registry.json, and registry.yaml. It does not change a dependency manifest, lockfile, Dockerfile, workflow, or pipeline file covered by…
Secrets, Payloads & Pii In Logs	✅ Passed	The pull request changes only plugin status values in registry.yaml and registry.json, plus the generated README table. No changed line emits logs, errors, telemetry, stack traces, request data, c…
New Dependency Scrutiny	✅ Passed	No new dependency, GitHub Action, or Buildkite plugin was added. The PR changes only the antivirus status from being-tested to tested in README.md, registry.json, and registry.yaml; no depen…
Install & Build-Time Code Execution	✅ Passed	PASS — The authoritative diff changes only the antivirus status in README.md, registry.json, and registry.yaml. The patch adds no installer, shell command, CI step, Dockerfile, Go environment setting,…

Full details: Ai Contribution Disclosure

Explanation

The PR body contains only a CodeRabbit-generated summary. It lacks the required lowercase ## what, ## why, and ## refs sections. It also contains the prohibited AI-tool signature text coderabbit.ai. The reviewed diff is a small status-only change across three files with three incremental commits, so the missing-disclosure exception for trivial changes does not remove these separate body and signature violations.

Resolution

Replace the PR body with concrete ## what, ## why, and ## refs sections. Add ## ai disclosure with the required concrete tool/version, assistance, and review fields if AI materially assisted. Remove the CodeRabbit-generated comment, Summary by CodeRabbit text, and other AI attribution or signature lines.

Full details: Renovate: Config Present And Valid

Explanation

Renovate configuration check fails. The PR changes root files (README.md, registry.json, and registry.yaml), so the check triggers. The PR head contains none of the accepted files: renovate.json, renovate.json5, .github/renovate.json, or .github/renovate.json5. Therefore, Check 1 emits the specified warning. Checks 2 and 3 cannot pass without a configuration file.

• Fix all pre-merge checks with AI

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

Autopilot is currently an internal CodeRabbit preview.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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