Manifest
commercialThe section your link pointed to isn't on Manifest's page any more, so we've brought you to the top.
Manifest secures the software and AI supply chains behind the technology enterprises build and buy, with inside-out visibility across dependencies, binaries, vulnerabilities, provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build., and AI models.
Summary
Manifest is a commercial appsec platform that tracks third-party supplier risk alongside first-party code through SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. analysis. It runs as a service, with teams uploading existing SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. or binaries for products that lack one — including C++, unmanaged code, and embedded systems where traditional SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. tools fall short — and having those results rolled into a per-supplier record. Each vendor gets a risk score aggregated from its assets, letting procurement and third-party risk teams rank suppliers against each other and drill into a single vendor's full footprint of components and open vulnerabilities in one view. This targets product security, DevSecOps, and vendor risk teams rather than SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts chasing live incidents, and the CLI's supplier-tagging option suggests it's meant to slot into existing upload pipelines. The documentation was last updated 11 months ago, with steady feature releases since.
Manifest secures the software and AI supply chains behind the technology enterprises build and buy, with inside-out visibility across dependencies, binaries, vulnerabilities, provenance, and AI models.
How Manifest helps
Which open-source components in my code carry a known vulnerability I have not fixed?
scans the SBOM generated from uploaded software against vulnerability data and lists affected components by product, ranked by severity and impact
Which of my vendors are the riskiest part of my software supply chain right now?
rolls up every asset in a supplier's portfolio into a single comparable risk score based on vulnerability count, asset count, and how recently it was updated
Can I get an SBOM for a vendor's product that never shipped one?
generates an SBOM directly from the binary, covering C++, unmanaged code, and embedded systems that traditional source-based scanning cannot reach
Which third-party products in my inventory are mine to fix versus a vendor's problem to fix?
shows first-party and third-party components side by side on the same vulnerability and component pages, visually distinguished by what was built versus bought
Is the software I built last quarter still safe today?
continuously monitors uploaded SBOMs and AI models for newly disclosed vulnerabilities and surfaces emerging risk as it appears, without a re-upload
What do I hand an auditor to prove what is in my product and how it is secured?
exports consolidated SBOMs, vulnerability reports, and license reports as compliance artifacts, delivered automatically once workflows are set up
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 Manifest, 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 Manifest 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…
Website history
manifestcyber.com, every changeManifest's home page and 25 more pages as they looked each month from November 2022 to October 2026: 36 renders, 5 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
2 entries
No entries match these filters.
- October 20261
- August 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.