fix(security): update dependencies

dev.Dockerfile

@@ -1,17 +1,18 @@
 ARG ALPINE_IMAGE=alpine:3.21@sha256:48b0309ca019d89d40f670aa1bc06e426dc0931948452e8491e3d65087abc07d
+ARG UV_IMAGE=astral/uv:0.12.7-alpine3.23@sha256:d0d7c7a05e4d9270b97392da2204371581b431287f2ae959e4aef715c86f9efc
 
-FROM astral/uv:alpine AS build
+FROM ${UV_IMAGE} AS build
 
 WORKDIR /root/cloudsmith-cli
 
 RUN apk add --no-cache binutils
 
-ADD bin bin
-ADD cloudsmith_cli cloudsmith_cli
-ADD packaging packaging
-ADD pyproject.toml pyproject.toml
-ADD uv.lock uv.lock
-ADD VERSION VERSION
+COPY bin bin
+COPY cloudsmith_cli cloudsmith_cli
+COPY packaging packaging
+COPY pyproject.toml pyproject.toml
+COPY uv.lock uv.lock
+COPY VERSION VERSION
 
 ARG CLOUDSMITH_CLI_VERSION
 ARG PYTHON_VERSION=3.14

pyproject.toml

@@ -47,16 +47,22 @@ dependencies = [
     "keyring>=25.4.1",
     "keyrings-alt>=5.0.2",
     "keyrings-cryptfile>=1.3.9",
+    # Security floors for MCP's runtime dependency graph. Keep these explicit:
+    # downstream installers do not consume uv.lock and could otherwise select
+    # vulnerable transitive versions allowed by MCP's broader constraints.
+    "cryptography>=50.0.0",
     "mcp==1.28.1",
+    "pydantic-settings>=2.14.2",
     # The crypto extra must be declared here: the OIDC flow verifies JWT
     # signatures, and a bare PyJWT requirement would let the
     # standalone-binary build resolve without the cryptography wheels.
-    "PyJWT[crypto]>=2.0.0",
+    "PyJWT[crypto]>=2.13.0",
     "python-toon==0.1.2",
     "requests>=2.18.4",
     "requests_toolbelt>=1.0.0",
     "rich>=13.0.0",
     "semver>=2.7.9",
+    "starlette>=1.3.1",
     "urllib3>=2.5",
     "tomlkit>=0.15.0",
 ]