Typesafe Daggerverse
August 24, 2026 · View on GitHub
Shared Dagger modules.
Add as a dependency to another Dagger module:
$ dagger install github.com/typesafe-ai/daggerverse/uv
$ dagger install github.com/typesafe-ai/daggerverse/github
$ dagger install github.com/typesafe-ai/daggerverse/twingate
$ dagger install github.com/typesafe-ai/daggerverse/pinact
$ dagger install github.com/typesafe-ai/daggerverse/zizmor
$ dagger install github.com/typesafe-ai/daggerverse/deptry
Modules
| Module | Description |
|---|---|
uv | Tooling for uv-managed Python projects: audit locked dependencies (uv audit) across every workspace, build minimal containers with a package's deps installed (parsing uv.lock to resolve local members, remote deps first for caching, with extras/groups and Dagger SDK codegen), and build/export relocatable virtual environments that run in a fresh container with no Python of its own. |
github | GitHub utilities for Dagger pipelines. Includes a status monitor that polls commit statuses and check runs until a final verdict is reached. |
twingate | Twingate HTTP CONNECT proxy as a Dagger service. Runs the client in userspace networking mode (--tun off) so no root or NET_ADMIN is required. Authenticate with a service key, then bind the proxy to any container via bind_proxy. |
pinact | Check that GitHub Actions are pinned to full-length commit SHAs using pinact. Runs in check-only mode (--check). Optionally pass a GitHub token for API-based SHA resolution and comment verification. |
zizmor | Static analysis of GitHub Actions for security issues using zizmor. Detects template injection, credential leaks, excessive permissions, and more. Runs offline by default; pass a GitHub token for online audits. |
deptry | Lint Python dependency issues — unused, missing, misplaced, and transitive dependencies — using deptry. A single check fans out across every uv project (pyproject.toml) in the source tree, running deptry per project in parallel. |