[comment] better UVP

Author: 11notes

project.md

@@ -13,12 +13,14 @@ socket-proxy-1  |     user: "0:991"
 ${{ content_uvp }} Good question! All the other images on the market that do exactly the same don’t do or offer these options:
 
 ${{ github:> [!IMPORTANT] }}
-${{ github:> }}* This image runs the proxy part as a specific UID/GID (not root), all other images run everything as root
-${{ github:> }}* This image uses a single binary, all other images use apps like Nginx or HAProxy (bloat)
-${{ github:> }}* This image has no shell since it is 100% distroless, all other images run on a distro like Debian or Alpine with full shell access (security)
-${{ github:> }}* This image does not ship with any CVE and is automatically maintained via CI/CD, all other images mostly have no CVE scanning or code quality tools in place
-${{ github:> }}* This image has no upstream dependencies, all other images have upstream dependencies
-${{ github:> }}* This image exposes the socket as a UNIX socket and TCP socket, all other images only expose it via a TCP socket
+${{ github:> }}* This image runs the proxy part as a specific UID/GID (not root), most other images run everything as root
+${{ github:> }}* This image uses a single binary, most other images use apps like Nginx or HAProxy (bloat)
+${{ github:> }}* This image has no shell since it is 100% distroless, most other images run on a distro like Debian or Alpine with full shell access (security)
+${{ github:> }}* This image does not ship with any critical or high rated CVE and is automatically maintained via CI/CD, most other images mostly have no CVE scanning or code quality tools in place
+${{ github:> }}* This image is created via a secure, pinned CI/CD process and immune to upstream attacks, most other images have upstream dependencies that can be exploited
+${{ github:> }}* This image contains a proper health check that verifies the app is actually working, most other images have either no health check or only check if a port is open or ping works
+${{ github:> }}* This image exposes the socket as a UNIX socket and TCP socket, most other images only expose it via a TCP socket
+${{ github:> }}* This image works as read-only, most other images need to write files to the image filesystem
 
 If you value security, simplicity and the ability to interact with the maintainer and developer of an image. Using my images is a great start in that direction.