OpenQodex icon

OpenQodex

openqodex/openqodex · v0.22.0 · Development & Workflow

by openqodexScan grade: GoodAwesome AI Plugins

Open source AI code review for coding agents: a separate reviewer process checks each change before git push, with plugins for Claude Code, Codex, and Cursor

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is OpenQodex a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • Claude Code
  • Cursor
  • 1 skill
  • 1 MCP server

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Apache-2.0

Check before relying on it

  • Some security checks did not finish: Cisco skill scan and Cisco MCP scan. See the evidence
  • The publisher has not verified ownership on HOL.

What is OpenQodex?

OpenQodex is a published development & workflow plugin for AI coding agents that works with Claude Code and Cursor, developed by openqodex and distributed through the HOL AI plugin registry. Open source AI code review for coding agents: a separate reviewer process checks each change before git push, with plugins for Claude Code, Codex, and Cursor.

Canonical slug
openqodex/openqodex
Version
v0.22.0 · updated Nov 20, 2026

Registry snapshot

Owner verification
Not verified
Marketplace source
.claude-plugin/marketplace.json
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
Yes
1 bundled skillRead, copy or download each SKILL.mdOpen skills

Trust and security

Trust & reputation

73

HOL Trust Score

Per-metric points (0–100 each) combined via a weighted average into the overall score.

Installability
100/100
Maintenance
30/100
MCP server setup
100/100
Plugin Security
83/100
Provenance
70/100
Publisher Quality
75/100

Provenance

Plugin root
plugins/claude-code
Source repo
https://github.com/openqodex/openqodex
Source commit
ffa62b5a08df…
Publisher verified
No
Owner verified
Not owner verified
Agent Plugins 1.0
Not detected

Continuous scanner CI not detected

This plugin remains listed. Its overall trust score is reduced by 10% because security checks are not maintained in the source repository's CI.

Optional: maintain the scanner in the source repository's CI to receive the full trust score. Listing does not require that change.

README badge not detected

Plugin owners can add the HOL badge to the repository README from Guard Plugins. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Needs review
Security result
83
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
B · Good
Version
3.24.2
codex:hol-plugin-scanner-qD5ZFo / cisco-skill-scanner: failedcodex:hol-plugin-scanner-qD5ZFo / cisco-mcp-scanner: unavailable

[claude:.] Claude Plugin

18/18

5 checks

[claude:.] Security

14/20

6 checks

[claude:.] Operational Security

N/A

5 checks · not applicable

[claude:.] Code Quality

10/10

2 checks

[codex:.] Manifest Validation

25/31

9 checks

[codex:.] Security

14/20

9 checks

[codex:.] Operational Security

N/A

5 checks · not applicable

[codex:.] Best Practices

9/12

5 checks

[codex:.] Marketplace

N/A

3 checks · not applicable

[codex:.] Skill Security

5/5

4 checks

[codex:.] Code Quality

10/10

2 checks

Published advisories

None matched in GitHub security advisories, checked . This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

lowsecuritySECURITY_MD_MISSINGReported 2 times

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowsecurityLICENSE_MISSINGReported 2 times

Plugins should ship a LICENSE file so consumers can review usage rights.

Add a LICENSE file that matches the manifest license metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_SHORTDESCRIPTION

The interface object is missing a valid "shortDescription" value.

Add a valid "shortDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_LONGDESCRIPTION

The interface object is missing a valid "longDescription" value.

Add a valid "longDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CATEGORY

The interface object is missing a valid "category" value.

Add a valid "category" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CAPABILITIES

The interface object is missing a valid "capabilities" value.

Add a valid "capabilities" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_WEBSITEURL

The interface field "websiteURL" must use HTTPS or point to a safe in-repo asset.

Update "websiteURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in Claude Code

Install through the Claude Code plugin marketplace.

Claude Code plugin docs

Optional: install HOL Guard for Claude Code first, so it can check this plugin's tools on your machine before Claude Code uses them.

  1. 1

    Add the marketplace

    Run this inside a Claude Code session. It registers the marketplace manifest shipped at the repository root. If the repository ships none, add the generated entry from the Advanced section below first.

    claude code
  2. 2

    Install the plugin

    Installs the openqodex entry from the openqodex marketplace.

    claude code
  3. 3

    Scripted alternative

    Non-interactive equivalent for scripts and CI pipelines. Add --scope project to pin the install to one repository.

    shell
  4. 4

    Check it is installed

    Lists installed plugins. The entry should appear as enabled.

    shell

To remove it later, run claude plugin uninstall openqodex@openqodex.

Did setup work in Claude Code?

No setup reports for Claude Code yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W46, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "name": "openqodex",
  "displayName": "OpenQodex",
  "version": "0.22.0",
  "description": "Code review before you push, inside Claude Code. One command runs the scanners that fit your change (Semgrep, Gitleaks, OSV-Scanner, ShellCheck, Ruff and more) on the lines you changed for security vulnerabilities, hardcoded secrets, vulnerable dependencies and lint errors. It then starts a separate reviewer, a fresh Claude Code or Codex process that checks every scanner finding and is given every changed line, and scripts check the reviewer's answer. Use after writing or changing code and before git push. Free and open source, on your own Claude Code or Codex login, with no other key or account.",
  "author": {
    "name": "Qodex",
    "url": "https://qodex.ai"
  },
  "homepage": "https://qodex.ai/openqodex",
  "repository": "https://github.com/openqodex/openqodex",
  "license": "Apache-2.0",
  "keywords": [
    "code-review",
    "ai-code-review",
    "security",
    "sast",
    "secret-scanning",
    "static-analysis",
    "lint",
    "pre-push",
    "semgrep",
    "gitleaks"
  ],
  "icon": "./assets/avatar-1024.png",
  "privacyPolicyUrl": "https://github.com/openqodex/openqodex/blob/main/docs/privacy.md",
  "interface": {
    "displayName": "OpenQodex",
    "developerName": "openqodex"
  },
  "skills": "./",
  "mcpServers": "./.registry/mcp.json",
  "holManifestOrigin": "repository",
  "registryIndexVersion": 9
}

Marketplace source

Repo URL
https://github.com/openqodex/openqodex
Marketplace path
.claude-plugin/marketplace.json
Source path
plugins/claude-code
Install policy
Unspecified

Skills

1 SKILL.md file ship with this plugin. Preview, copy, or download each one, then install them with the Skills CLI.

Share
skills-cli
  • openqodex

    skills/openqodex/SKILL.md

    Code review for the current change, before it is pushed. One command runs the security, secret, dependency and lint scanners that fit the changed files, a separate reviewer that checks every scanner finding and is given every changed line, and prints a short receipt with the path of the full report. Use before every git push, when asked for a code review, a security scan, or to review changes, a diff or a pull request, and when a push was blocked or warned by OpenQodex.

    Raw SKILL.md

File inventory

.claude-plugin/plugin.json

file

1,224 bytes

67634bdc97597424…

.codex-plugin/plugin.json

plugin-manifest

1,286 bytes

11f3c4726149b253…

.mcp.json

file

123 bytes

2de9ed10fe1f5869…

.registry/mcp.json

mcp-config

85 bytes

4f0dae317f3c6d4c…

hooks/hooks.json

file

271 bytes

6b96155867a660f0…

README.md

file

4,173 bytes

a7c8a2e8013f71dd…

skills/openqodex/SKILL.md

skill

11,014 bytes

936604a7fe318427…

OpenQodex — Frequently asked questions

What is OpenQodex?
OpenQodex is an AI plugin in the HOL registry. Open source AI code review for coding agents: a separate reviewer process checks each change before git push, with plugins for Claude Code, Codex, and Cursor.
How do I install OpenQodex?
Install OpenQodex in your harness: Claude Code — /plugin marketplace add openqodex/openqodex; Cursor — npx [email protected] add openqodex/openqodex; Any agent — npx [email protected] add openqodex/openqodex. Full step-by-step guidance is on the HOL plugin page.
How do I install OpenQodex in HOL Guard?
To install OpenQodex in HOL Guard, start with hol-guard plugin install openqodex/openqodex --apply. The complete step-by-step install guide for HOL Guard is on the HOL plugin page.
How do I install OpenQodex in Claude Code?
To install OpenQodex in Claude Code, start with /plugin marketplace add openqodex/openqodex. The complete step-by-step install guide for Claude Code is on the HOL plugin page.
How do I install OpenQodex in Cursor?
To install OpenQodex in Cursor, start with npx [email protected] add openqodex/openqodex. The complete step-by-step install guide for Cursor is on the HOL plugin page.
How is the Trust Score for OpenQodex computed?
OpenQodex has a HOL Trust Score of 73 out of 100. The score is a weighted sum of six components from a static scan of the source, capped for high-severity findings and adjusted by two disclosed policies. Memberships and payments are not inputs, and a scan is not a safety guarantee. Full breakdown: https://hol.org/registry/plugins/openqodex%2Fopenqodex/trust
Who publishes OpenQodex?
OpenQodex is published by openqodex and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W46. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.

Reviews and similar plugins