VSecM
VMware Secrets Manager (VSecM) is a lightweight, self-hosted secrets manager that protects credentials and API keys in edge and resource-constrained…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
15/100 Low
- Maintained
- 0GitHub repository is archived
- Popular
- 45174 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 07 serious findings, 5 minor, tests, OpenSSF Scorecard 7.1/10
Based on 4 of 5 factors.
Security check: 7 serious findings
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.35.0, which has a known critical vulnerability (Go)
Automated checks on commit 919b183, 7 Nov 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 174
- Open issues
- 94
- Last commit
- 2025-11-04
- Latest release
- v0.28.1
- License
- BSD-2-Clause
- Activity
- stale
Checked today - source: GitHub (vmware-tanzu/secrets-manager)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Project status: active and stable VSecM v0.x is stable, production-ready, and actively maintained. The core team is also developing SPIKE, a next-generation SPIFFE-native secrets manager, but VSecM remains active and open to contributions. source
- Secret delivery: Sidecar and Init container patterns VSecM injects secrets into workloads using two delivery patterns: a Sidecar container for runtime delivery and an Init container for startup delivery. Pick the pattern that matches when your workload needs the secrets. source
- Project status The README states vSecM v0.x is stable, production-ready, and actively maintained, while maintainers are developing SPIKE, a next-generation SPIFFE-native secrets manager. source
- Project status update VSecM v0.x remains stable, secure, and production-ready; maintainers are also developing SPIKE, a next-generation option. source
- Installation Install with the vsecm Helm chart (see the ArtifactHub link); VSecM injects secrets into your workloads via sidecar or init containers. source
- Project status (SPIKE successor) VSecM v0.x is stable and production-ready; the core team is now focusing on SPIKE, a next-generation SPIFFE-native successor. VSecM still welcomes community contributions. source
Fetched 30 days ago - each note links to its source
Variants
Alternatives (1)
- Vault by HashiCorp - Enhances security by managing secrets like tokens and passwords through centralized storage, access control, and encryption, ensuring data…
Checked 54 days ago - source: AlternativeTo
Common questions
Does VSecM rely on traditional SSL certificates for workload authentication?
No. VSecM uses SPIFFE as its identity control plane for secure workload authentication, eliminating the need for traditional SSL certificates.
Are VSecM secrets kept in memory?
VSecM stores sensitive data in memory and encrypts any data saved to disk.
How can Kubernetes workloads retrieve secrets from VSecM?
Documented use cases include using a VSecM sidecar, an init container, the VSecM SDK, mounting secrets as volumes, and mounting Kubernetes secrets.
Can VSecM be used with a CLI or SDK?
The documentation lists a VSecM CLI and a VSecM SDK for installation and use.
Answers sourced from github.com, vsecm.com, vsecm.com
Community
Collected 48 days ago - public community threads