DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a GitHub scanner to your review after approval with Openqodex

Configure a compatible scanner from GitHub, approve it, and run it in your reviews.

Remote script. The trust step downloads a release asset and then runs its command on your machine, so read the shown command before answering yes.

Who it is forA security-minded developer who wants a scanner beyond the 22 built-in ones in one repository.

The problemThe built-in scanners may not cover a check your team needs, and adding one safely takes care.

The outcomeThe scanner runs in your next review only after you approve its exact entry.

What you need first

  • Node 22 or newer, and git
  • macOS or Linux (no test runs on Windows or WSL)
  • Claude Code or Codex installed and logged in for a full review
  • A repository you can run commands in

Steps

  1. Add the scanner under scanners and custom in .openqodex/config.yaml, with its source, run command and target.
  2. Run npx openqodex trust and answer yes only after you read what it will run.
  3. Run npx openqodex scan --only custom:bearer to see the scanner work.
  4. Run a review, and confirm the custom scanner's findings appear in the output.

Prompt for your agent

In the repo at <path>, add the Bearer scanner from https://github.com/Bearer/bearer as a custom scanner in .openqodex/config.yaml. Do not run `openqodex trust` until I approve; then run `npx openqodex scan --only custom:bearer` and report whether it produced findings.

Caveat. The Bearer CLI is under the Elastic License 2.0, which is not an open source licence, and a fresh GitHub-hosted runner skips approved custom scanners.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page