Why it matters
Quality & Security tabs gives ForkMesh a concrete mechanism for repository health, checks, and advisories presented next to the code. Per-repository quality and security views keep checks, advisories, and repository health next to the code they describe.
Delivery metadata is part of a project, not a separate dashboard that should disappear during a migration. In ForkMesh, quality & Security tabs addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles quality & Security tabs through the same split it uses across the product: ForkMesh keeps runs, logs, artifacts, releases, quality signals, installers, and downloads close to the mirrored repository.
The behavior is intentionally narrow: Per-repository quality and security views keep checks, advisories, and repository health next to the code they describe. Outputs can be linked to commits and served by nodes instead of becoming opaque hosted-only assets.
Where it fits
Use quality & Security tabs when shipping, validation, and release assets need to remain attached to the preserved repository.
It pairs with the rest of CI, releases & distribution because Quality & Security tabs keeps repository health, checks, and advisories presented next to the code connected to the repository, its signatures, and the nodes that serve it.