How to use Vulngrep

You have just installed it. Follow this page from top to bottom once. After that, use the list to jump back to the step you need.

There is nothing to configure, and there is no Vulngrep account. Vulngrep checks the Java file you have open. It scans the rest of the project only when you ask.

1. The first minute

Free The underlines in the editor, and copying the guidance.

  1. Restart IntelliJ IDEA if it asked you to.
  2. Open a Java project that uses Spring or Spring Boot. IntelliJ IDEA 2025.2 or later.
  3. Open a Java file and write, or accept a suggestion from an assistant. Vulngrep checks that file as it changes.

You will not see a project scan start by itself. That is the intended behavior. A scan of the repository is a separate step, and it needs a license. The 14-day trial counts as that license while JetBrains says it is active.

A Personal or Organization license, including the trial, adds the Security view, baselines, reasoned risk acceptance, the commit check, and a one-step preview for a few exact shapes. Activate it in the IDE with the JetBrains account you used on the Marketplace. Section 11 shows the screen you get before that.

2. An underline

Free

  1. Find an underline in a Java file. It looks like IntelliJ's other inspections.
  2. Put the caret on it.
  3. Press Alt+Enter. On a Mac, that key is Option+Enter.

The menu explains the pattern, the potential impact, and what Vulngrep could not verify. The underline means the source matches a pattern. It does not mean the application has been exploited, and a file with no underline has not been declared safe.

One pattern also puts an icon in the gutter, beside the line number: Jackson configured to allow every class. The other findings are warnings and have no gutter icon.

A Kotlin file stays quiet. A reactive WebFlux application stays quiet. Vulngrep checks Java that uses Spring and Spring Boot.

If a check never appears, open Settings → Editor → Inspections → Vulngrep and confirm the five inspections are enabled. They are enabled when you install.

3. What an underline means

Vulngrep registers five inspections. Spring Security covers two patterns, so an underline can be any of the six below. The bold line is what it can mean. The rest is the source pattern.

  • A visitor's input is pasted into a database query. JPQL built by joining strings, then passed to EntityManager.createQuery.
  • Incoming data can name the class Jackson creates. Jackson 2 class-name typing, the older default-typing methods, or a validator that allows every class.
  • Requests that match no earlier rule are public. A Spring Security chain that ends in anyRequest().permitAll().
  • Other websites can submit your users' actions. CSRF protection switched off.
  • Any website can call the API. @CrossOrigin set to *.
  • Management endpoints may be open. Spring Boot Actuator paths allowed with permitAll(). A matcher that includes health is reported differently from one that does not.

A public page, a health check, or an open API can be intentional. Vulngrep shows the pattern and leaves that judgment to you.

4. Copy the guidance

Free Works from the editor. The same action is on the paid screens too.

  1. Put the caret on the underline and press Alt+Enter.
  2. Choose Copy fix prompt for an AI assistant.

Vulngrep copies a short excerpt of the original code and the guidance that belongs to that finding. The file does not change. Vulngrep does not call an AI, and it does not upload the excerpt.

Paste it only into a tool your company allows for that code. The excerpt can contain source and secrets. Vulngrep does not remove them, and it does not control clipboard history or clipboard sync.

If the action says the finding is stale, click in the file so IntelliJ refreshes it, or run the scan again, then copy again.

5. Preview one edit

License Personal, Organization, or the 14-day trial. The preview exists only for a few exact shapes, and only in the editor.

The steps are the same every time.

  1. Caret on the underline, then Alt+Enter.
  2. Read the diff IntelliJ shows. The file is still unchanged.
  3. Choose the action. One Undo puts the file back, including an import the edit added.

The Security view and the commit window can say a fix is available. They open the file. They never edit it. There is no Fix all.

The action you will see

  • Use a named query parameter — a simple SELECT … FROM Entity e WHERE e.field = query that concatenates one value. That value becomes a named parameter. A query with a different shape keeps the guidance only.
  • Choose a trusted CORS origin… — @CrossOrigin uses the literal *. You type one http:// or https:// origin. The field starts empty. Then the menu offers Apply chosen CORS origin or Cancel without editing.
  • Choose a restricted Jackson package policy… — specific Jackson 2 calls. You type a package prefix that ends in a dot, such as com.example.dto. Every class in that package and its subpackages becomes allowed. Then choose Apply chosen Jackson package policy or Cancel without editing. Jackson 3 keeps the guidance only.
  • Require authentication for all remaining requests (list public routes explicitly first) — anyRequest().permitAll() becomes authenticated(). Rules written earlier stay as they are. Put the public routes before anyRequest().
  • Require authentication for these Actuator endpoints (roles may still be needed) — a permitAll() whose matcher does not include health. A signed-in user is not the same as a user with a specific role. A matcher that includes health, or a broad path such as /actuator/**, has no such edit.
  • Re-enable CSRF protection (browser clients must send CSRF tokens) — csrf(...) is given a method reference, or a lambda whose only statement disables CSRF. Browser clients then have to send tokens. The older .csrf().disable() chain has no such edit.

If the action is missing from the menu, this shape is outside the preview. Copy the guidance, or edit the code yourself. A missing action is the intended result for that code. Applying a preview does not prove the change is sufficient, or that the project is secure.

6. Scan the repository

License Personal, Organization, or the 14-day trial.

  1. Open View → Tool Windows → Vulngrep Security.
  2. The window opens on an explanation. It has not scanned anything.
  3. Press Scan entire project. Wait until the status says the scan finished.

The window has three tabs.

  • Project findings — the scope box says Entire project or Current file. Entire project reads Java source roots. Current file is the Java file that was active when you pressed Scan current file. The name stays on that file if you then open another one.
  • Current changes — press Review current changes. Vulngrep reads the whole current file for each changed Java file, including lines you did not select in the diff. It does not read Git's staging area. A project that is not in a VCS explains that, and you use Entire project instead.
  • Reviewed — baselines and recorded decisions. Section 9.

Include tests is off until you check it. The check applies to the next scan. The counts already on screen still describe the previous scan, and the window asks you to scan again. Generated code, libraries, and excluded folders stay out either way.

Cancel scan stops the scan that is running. Switching tabs does not start a new one.

Read the status before you read the count. Partial, failed, cancelled, or still indexing is an unfinished scan. No rows on an unfinished scan is not a clean result. A finished scan with no rows means these patterns were not found. It does not mean the application is secure.

Open the Coverage tab on the same result. Every requested file is listed as complete, partial, skipped, failed, cancelled, or not analyzed, with the reason. A disabled Vulngrep inspection is named there. A baseline and an accepted risk both require all five checks enabled on a finished project scan.

7. Read a finding

The Findings table columns are Review, Potential impact, Rule, Location, and Editor severity. Rows that need a look are sorted above rows you have already recorded.

  1. Select a row. The text under the table is the message, the evidence, what is still unknown, and the guidance.
  2. Press Open source, double-click the row, or press Enter. IDEA opens that line.

If the file changed after the scan, IDEA still opens the file, the old line is not selected, and the window tells you to scan again. A deleted or moved file says the location is unavailable.

The same finding can appear in Project findings and in Current changes. Those counts are separate. Do not add them together.

8. Decide

Each finding gets one of three treatments. Record the reason when you leave the code as it is. Hiding the underline is a different action, described at the end of this section.

Change the code

Use a preview from section 5 when the menu offers one. Otherwise edit the file yourself. The underline updates as the open file changes. The project table updates when you scan again.

Hand the guidance to an assistant

Use section 4. Review whatever the assistant writes. Vulngrep checks the file again as it changes.

Leave it, and write down why

  1. Run Scan entire project and wait until it finishes, with all five Vulngrep inspections enabled. A current-file scan is not enough for this step.
  2. Select the finding and press Accept risk….
  3. Type why this pattern is acceptable here. One character minimum, 4000 maximum.

The row stays in the table, marked Accepted risk. The underline stays in the editor. Accept risk is your note, on this computer, in this IDE workspace. It is not shared with the team, and it is not an audit log. Reopen sends it back for review and keeps the reason visible.

If the code, a dependency, or another file in the scanned project changes, the note can return to needing review. After you restart IDEA, the note is Unverified until you run Scan entire project again and the project still matches. If the dialog was open while the file changed, Vulngrep refuses the decision. Scan again, then decide again.

To hide an underline, use IntelliJ's usual inspection suppression on that line. That removes it from the editor and from later scans. It does not store a reason. Accept risk and suppression do different jobs. Use Accept risk when you want the finding to remain visible with an explanation.

9. New and old

License Same license as the scan. Do this once you have looked at the current project and want later scans to separate new patterns from ones already there.

  1. Run Scan entire project and wait until it finishes, with all five checks enabled.
  2. Open the Reviewed tab.
  3. Press Create baseline….

Findings in that inventory become Existing. A finding that appears afterward is New. Before a baseline exists, findings are Unreviewed. Creating a baseline does not accept any risk.

Replace baseline… records a new inventory. Reasons you already accepted stay. Reset review state… removes the baseline and the reasons from this workspace after you confirm. Your code and your inspection settings stay as they are.

The Review column uses these words, from the top of the table downward: Needs review, Unverified, New, Unreviewed, Existing, Accepted risk.

10. A commit

License On by default for commits you make inside IntelliJ IDEA.

In the commit options, Review security with Vulngrep is checked. Include test sources in security review is a second checkbox, and it starts unchecked. Both are your personal settings. They are not stored as a rule for the team.

When you commit, Vulngrep checks the Java files you selected. It checks each whole file as it is now, including lines you left out of the diff. It does not check what Git has staged. A commit from a terminal, or a push of a commit that already exists, is not checked. Files that are not Java are outside this check.

  • Every selected file was checked, and there are no findings: the commit continues.
  • There are findings: a dialog opens. Review is the focused button. Continue this commit lets this attempt through. That does not accept the risk, does not change the baseline, and does not remove the underline. Cancel commit stops. Open source and cancel commit opens the line and stops the commit.
  • The scan did not finish: the continue button reads Continue without complete review…. You confirm a second time. The confirmation says this does not mark the code as safe.

Existing findings and accepted risks are still shown, and this commit still asks you to continue or cancel. If you edit a file while the dialog is open, press Retry scan before you continue. You can uncheck Review security with Vulngrep when you do not want the check.

11. A license

Without a license, Vulngrep Security shows a short explanation and the button Activate a license in the IDE. The five underlines and Copy fix prompt for an AI assistant keep working.

Press that button and sign in with the JetBrains account that owns the license or the trial. Vulngrep has no login of its own, and it does not count the 14 days. JetBrains ends the trial.

After 12 paid months in a row, you keep a working copy of the version you had. Updates stop. If you stop paying sooner, the Security view, baselines, risk acceptance, commit review, and the one-step previews switch off. The five checks and the copy action stay.

Prices, the trial, and company seats are on the pricing page. Questions go to hello@vulngrep.com.

12. Limits

  • Java with Spring and Spring Boot, tested with Spring Boot 3 and 4. Kotlin and reactive WebFlux are outside the checks.
  • Analysis stays on your computer. The license check is JetBrains'. The copy action is the step that puts source on the clipboard, and it runs only when you choose it.
  • A quiet file, a finished scan, or an applied preview is a statement about these patterns. It is not a statement that the application is secure.
  • Shapes the preview does not recognize keep the guidance. Vulngrep will not invent a CORS origin or a Jackson package for you.
  • A baseline and an accepted risk live in this IDE workspace. Another developer, another machine, and a fresh checkout do not inherit them.