Work with me
Custom plugins and inspections
For teams that want their own rules enforced in the IDE and in CI. Static-analysis inspections tailored to your codebase, delivered as a plugin your developers install — with a fixed scope, a fixed price and a test for every inspection.
What does a custom static-analysis inspection catch that a generic linter does not?
A generic linter only knows general rules; a custom inspection knows your codebase, so it can flag your own internal APIs, secret formats, security patterns and architecture rules that a general linter cannot express. The inspections are delivered as a JetBrains plugin your developers install, with a test for every inspection and a written description of what each one flags and why.
Can the same inspections run in CI, not only in the IDE?
Yes. The inspections can run in GitHub Actions or GitLab CI, so a pull request fails on the same rule the IDE flags as developers type, and the plugin can be served from a private plugin repository your team updates from.
Who it is for
- Teams with internal APIs, frameworks or conventions that generic linters do not know about.
- Companies that want secret formats, security patterns or architecture rules caught in the IDE, as developers type.
- Platform teams that need the same checks to run in CI, not only on each developer’s machine.
What gets built
- Inspections tailored to your codebase. Internal APIs, secret formats, security patterns and architecture rules that a generic linter cannot express.
- Delivered as a plugin. Packaged as a JetBrains plugin your team installs, with a test for each inspection.
- The same checks in CI. The inspections can run in GitHub Actions or GitLab CI, so a pull request fails on the same rule the IDE flags.
- Private distribution. The plugin can be served from a private plugin repository your team updates from.
What you receive
- The plugin, with its source, and a test for each inspection.
- A written description of each inspection: what it flags, why, and its quick-fix when it has one.
- The CI configuration, when CI is in scope.
- One round of follow-up questions by email after delivery.
How it works
- You describe the rules you want enforced and share example code that should and should not trigger them.
- Within 2 business days you receive the scope in writing: the inspections, whether CI is included, delivery date and price.
- 50% is paid when the work starts and 50% on delivery.
- The work is asynchronous: email and a pull request. A call is available if you prefer one.
Price
- USD 7,500, fixed, for up to 3 inspections, packaged as a plugin with a test for each, delivered within 10 business days.
- From USD 15,000 for a full plugin: the inspections also run in GitHub Actions or GitLab CI and the plugin is served from a private plugin repository. The delivery date is set in the scope.
- Paid by international bank transfer in USD, against an invoice.
Terms in short
- The plugin and its source are yours once the invoice is paid.
- Your code and your data stay confidential. Signing your NDA is fine.
- Liability is limited to the price paid.
Track record
- 146 plugins in this catalog, built and shipped on the JetBrains Marketplace with the same inspection tooling: see the plugin catalog.
- Each ships with tests and is verified against the IDE versions it supports before release.
Start
- Email contact@gaphunterlabs.com with “Custom plugin” in the subject, or use the contact page. Describe the rules you want enforced and whether you need them in CI.