New v1.2.31

Plexicus v1.2.31: Smoother GitLab Onboarding & Reliable AI Pentest Model Selection

Connect GitLab repositories with fewer friction points — including nested groups and broader access roles — and count on dependable AI Pentest runs with corrected model selection.

🛠 Improvements

  • Broader GitLab Repository Visibility: When you connect a GitLab account, Plexicus now surfaces every project your account can read — including those where you hold a Reporter or Developer role — so your repository picker no longer silently excludes repos you should be able to scan.
  • Nested GitLab Group Support: Repositories living deep inside nested GitLab group hierarchies now clone and scan correctly. You no longer encounter projectnotfound errors when a repo’s full namespace path includes multiple group levels.

🔧 Fixes

  • AI Pentest Model Selection: AI Pentest now selects the correct AI model for every run, respecting your BYOAI Smart-model override when configured and otherwise defaulting to a proven, tool-call-compatible model. Previously, a fallback could select a model that produced unparseable output, causing the pentest agent to exhaust its iteration budget and return incomplete results with zero findings.
  • GitLab Self-Hosted URL Handling: If your connected GitLab self-hosted URL is stored in a malformed format, Plexicus now gracefully falls back to the default GitLab host so that live repository listing continues to work instead of silently breaking.
Qualification

Check whether AI Swarm Pentest fits your environment.

Share the minimum context. We will review the scope and tell you the next commercial step.

Before submitting — verify you fit

Teams with fewer than 50 developers: start a 14-day Trial instead of booking a demo. Start a 14-day Trial →

0 / 280

No commitment. If you don't fit, we'll tell you.

SAMPLE HANDOVER · ILLUSTRATIVE

Sample evidence handover

A trimmed view of what your team receives at the end of an AI Swarm Pentest engagement. Real engagements include full technical evidence, executive narrative, and a remediation plan.

VALIDATED FINDING Evidence attached

Server-Side Request Forgery in webhooks/receiver

demo-project/sample-app · src/webhooks/receiver.py:42

SeverityHigh CVSS 3.18.6 Priority79 Confirmedvia replay

Untrusted caller-supplied URLs reach an internal egress without an allowlist. Replayed in a sandbox against a fresh authorised target — the same control was validated to fail twice.

REVIEWER-READY REMEDIATION Merge-ready PR

Validate the target URL against an allowlist of permitted hostnames. Reject private/internal IP ranges. Enforce HTTPS only.

plexicus/remediation/webhooks-ssrf 3 changed · 0 new files
42resp = requests.get(target_url)
42+if not is_allowed_host(target_url):
43+  raise WebhookRejected(target_url)
44+resp = requests.get(target_url, timeout=5)
Every engagement hands over:
  • Executive briefing
  • Validated findings list
  • Merge-ready PRs
  • Compliance mapping (NIS2 · DORA · CRA)