Xygeni
Next commercialThe section your link pointed to isn't on Xygeni's page any more, so we've brought you to the top.
Xygeni is a software supply chainsoftware supply chainThe dependencies, tools and processes used to build and deliver software. Compromising one part can affect the products or organizations that rely on it. security platform that detects threats, misconfigurations, and vulnerabilities across CI/CD pipelines, code repositories, and dependencies.
xy-dast scan -u <url> xyg --report-type junit-xml
Summary
Xygeni is a commercial software supply chain security platform that detects threats, misconfigurations, and vulnerabilities across CI/CD pipelines, code repositories, and dependencies. It is not available on-premises, functioning as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. offering. It is intended for developers and application security teams. The platform has seen seven releases within the tracked period, with the last release occurring 75 days ago.
Xygeni is a software supply chain security platform that detects threats, misconfigurations, and vulnerabilities across CI/CD pipelines, code repositories, and dependencies.
How Xygeni helps
Which of my dependencies pulled in a package with a known vulnerability?
scans the dependency tree across manifests and lockfiles and flags packages with known flaws, naming the transitive path that pulled each one in
Are there secrets or credentials sitting exposed in my repositories?
scans code and commit history for exposed keys, tokens, and credentials and reports the file and location where each was found
Which of my CI/CD pipelines have configuration weaknesses an attacker could exploit?
inspects pipeline definitions across the CI/CD system for misconfigurations, such as excessive permissions or unpinned actions, and lists each one against the pipeline it belongs to
Has anyone tampered with my build process or introduced unexpected changes?
tracks the components and steps that make up a build and flags deviations from the expected pipeline behavior or unauthorized modifications
Which open-source packages in my project carry risk beyond known vulnerabilities?
evaluates dependencies for signals like suspicious maintainer activity or malicious code patterns, not just published advisories
Where did a given threat enter my software supply chain?
correlates findings across code, dependencies, and pipeline activity to trace an issue back to the stage where it was introduced
Languages
Command line
2 commands for Xygeni, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
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 Xygeni, 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 Xygeni 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…
Releases
6 entries
No entries match these filters.
- June 20261
- December 20251
- September 20251
- June 20251
- April 20251
- March 20251
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 →