Plexicus
changelog-20261031-41e91c48 commercialThe section your link pointed to isn't on Plexicus's page any more, so we've brought you to the top.
Plexicus is an AI-powered application security platform that automatically detects, prioritizes, and remediates vulnerabilities across code, APIs, and cloud environments.
Summary
Plexicus is a commercial cloud-security platform that scans code repositories and registries to find, prioritize, and remediate vulnerabilities. It runs as a service, with onboarding flows for connecting GitHub and GitLab accounts, including multi-account and nested-group setups, and it aims at application security and DevSecOps teams rather than individual developers. Its capabilities span the pipeline from detection to fix: registry scanning surfaces exposed images, Multifactor Priority Scoring v2 and NVDNVDThe National Vulnerability Database, maintained by NIST, is the U.S. government repository of CVE records enriched with CVSS scores and metadata; cyber tools query it to drive vulnerability prioritization.-backed CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. data rank findings by real severity, and a remediation path called Codex Remedium applies AI-generated fixes, with a naming layer to keep BYOAI models consistent across the platform. That breadth places it in the broader cloud-security posture and remediation space rather than any single-purpose scanner. With 13 releases in the window we track, spanning onboarding, scoring, and remediation improvements, the project shows steady, active development.
Plexicus is an AI-powered application security platform that automatically detects, prioritizes, and remediates vulnerabilities across code, APIs, and cloud environments.
How Plexicus helps
Which images in my registries have exposed vulnerabilities before they ever reach a cluster?
scans registries directly and surfaces exposed images with their findings, independent of any deployment pipeline
Which of my vulnerabilities actually matter right now?
scores every finding with a multifactor priority model backed by NVD CVSS data, ranking by real-world severity rather than raw CVE counts
Can a finding be fixed without someone writing the patch by hand?
routes eligible vulnerabilities through an AI remediation path that generates and applies a fix directly
Are all my repositories across different accounts actually being watched?
onboarding connects multiple GitHub and GitLab accounts, including nested groups, so repositories under separate accounts or subgroups are covered rather than silently skipped
Which AI model produced a given remediation, when I'm using more than one?
applies a canonical naming layer to BYOAI models so a fix's origin stays identifiable even when several models are in play across the platform
Did tightening severity scoring change how my existing findings rank?
reruns findings against the NVD-backed CVSS data and the updated priority model, so severity shifts show up against the prior scores rather than being masked by a flat CVE rating
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Plexicus, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Plexicus puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What Plexicus connects to, runs on and detects, read from its release notes and docs. So far: 1 new supported platform.
1 change, tracked since Oct 1, 2026.
-
Oct 12026
new C# and .NET AI SAST coverage
With Razor
AI SAST now covers C#/.NET and Razor
Languages & runtimes 3
Nothing first seen in this window. That doesn't mean Plexicus shipped nothing, only that we found no record of it.
How we count
Read from 4 of 11 release notes and docs updates we hold for Plexicus. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Plexicus's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
11 entries
No entries match these filters.
- October 20266
- August 20264
- July 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →