Add QRStuff plugin to Tools & Integrations

[rushabh-qrstuff]

Plugin Submission

• Plugin Name: QRStuff
• Repository: https://github.com/qrstuff/codex-plugins
• Category: Tools & Integrations
• CI Workflow: .github/workflows/hol-plugin-scanner.yml added
• License: MIT
• Security Policy: Included (SECURITY.md)

Connects OpenAI Codex CLI agents to the hosted QRStuff MCP server to generate, customize, and manage QR codes.

[qodo-free-for-open-source-projects]

PR Summary by Qodo

List QRStuff in Tools & Integrations

📝 Documentation ✨ Enhancement 🕐 Less than 5 minutes

AI Description

• Adds QRStuff to the community Tools & Integrations catalog.
• Documents QR code generation, customization, management, and analytics capabilities.

High-Level Assessment

The single README entry is the repository's prescribed plugin-submission approach. Committing plugin bundles or generated catalog files was considered unnecessary because CI imports and regenerates them after verification.

Files changed (1) +1 / -0

Documentation (1) +1 / -0

README.mdAdd QRStuff to the plugin catalog +1/-0

Add QRStuff to the plugin catalog

• Adds an alphabetically placed Tools & Integrations entry linking to the QRStuff repository. The description highlights support for over 25 QR code types, customization, management, and scan analytics.

README.md

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can tweak Display preferences with a live preview to see your comment before it ships

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[kantorcodes]

The source scanner and per-PR checks are green, but this branch is based on Codex catalog main 7a62a714, while current main is 51124f68 (two commits behind). Please rebase onto current main, rerun the scanner and contribution checks, and request re-review once the branch is current.

[kantorcodes]

The source scanner and per-PR checks are green, but this branch is still based on Codex catalog main 7a62a714. Current main is e01550e0 after scanner-guide updates. Please rebase onto current main, rerun the scanner and contribution checks, and request re-review once the head is current.

[kantorcodes]

The source scanner and per-PR checks remain green, but this branch still targets Codex catalog main 7a62a714 while current main is 70983d15. Please rebase onto current main, rerun scanner/contribution/generated-artifact checks, and request re-review once the branch is current.

[kantorcodes]

Codex catalog main advanced to 2da64baa after the TokenChronicle artifact sync, while this branch still targets 7a62a714. The source scanner and PR checks remain green, but please rebase onto current main, rerun scanner/contribution/generated-artifact checks, and request re-review.

[kantorcodes]

Codex catalog main has advanced again to d1deab06 (docs: refresh plugin scanner submission guide), while this branch still targets 7a62a714. The source scanner and PR checks remain green, but please rebase onto current main, rerun scanner/contribution/generated-artifact checks, and request re-review before approval.

[kantorcodes]

Rechecked this one-line README addition against current Codex catalog main 90f0d46. The centralized scan is 86/100 (0 critical, 0 high, 0 medium, 2 low, 1 info), above the required 80-point threshold; source-repository scanner CI is optional for listing. Catalog validation, alphabetical checks, all contribution gates, and review-thread checks are clear, and the branch applies cleanly to current main. The earlier stale-base request is superseded by this clean applicability check. Proceeding with approval and squash merge.

[kantorcodes]

Centralized scanner score 86/100 clears the required 80 threshold; scanner CI is optional. The one-line README change merges cleanly with current main 90f0d46, all catalog/contribution checks pass, and no unresolved non-outdated review threads remain. Approved for squash merge.

[github-actions]

🎉 Hey @rushabh-qrstuff, your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

• Owner-verified badge on your plugin's registry listing
• Trust score visibility and analytics for your plugin
• Direct claim link to share with your community
• Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

1. Visit hol.org/guard/plugins
2. Find your plugin and click "Verify ownership"
3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.

[kantorcodes]

Hi @rushabh-qrstuff — a quick follow-up about your plugin qrstuff/codex-plugins.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.

[kantorcodes]

Hi @rushabh-qrstuff — a quick follow-up about your plugin qrstuff/codex-plugins.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.