Guided review

Bring one repository. Work through the security decision.

Run the first scan with the Helmwart team, examine the leading finding, and try the release gate in your workflow. This optional four-week evaluation is for AppSec and DevSecOps teams using MCP, n8n, LangGraph, or CrewAI.

The working sessions

From a first finding to a useful review.

Bring a repository and someone who can add a pull-request check in a pilot or non-production environment. We will work through what the result means and where it falls short.

  1. Setup · 25 minutes

    Read the first finding together

    Install Helmwart, run a local scan, and review the highest-ranked finding. Check its evidence against the system your team actually operates.

  2. Between sessions

    Try it in a real workflow

    Use findings, exceptions, and the release gate in a pilot CI check. Keep track of useful results, false positives, and unclear output.

  3. Weeks two and four

    Decide what earns its place

    Review what happened with the Helmwart team: which results helped a decision, what needs improving, and whether to keep the check in CI.

What the review is for

Evidence for your next decision.

Use the sessions to test whether a finding is credible, identify a control to try, and assess whether the release gate is useful to your team. Static results still need your engineering judgment.

Your feedback helps us improve the product. The evaluation does not certify a repository or approve a release.

Choose what you share with us.

Observation is manual and consent-based. The CLI does not send silent usage telemetry, and recording a scan is optional. You do not need to make a private repository public to apply.

Read what stays local and what is sent

Start the conversation

Apply for the guided evaluation

Tell us about your team and one repository. The Helmwart team will review your application and reply to your work email about fit and scheduling.

All fields are required. Share a repository link, not credentials or source code. Private repositories can stay private during qualification.

Your team
Your repository
Active frameworks — select at least one
Your review goals