ContainerSSH
/All repositories
Overview
HEALTH SCORE
Concerning*
Partial score (2/3 categories)
28out of 65
Development cadence is the lead risk. Maintainer coverage is present but not enough to offset the structural risk. Security & Supply Chain is unavailable, so weights were redistributed.
LIFECYCLE
Active
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Concerning*(28/65)
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Maintainer responsiveness
Median response time is 0 days, but most repositories have response times over 90 days.
Bus factor
Only 2 active maintainers currently have merge rights.
Organization Diversity
Contributors span 88 organizations.
Archived repositories are excluded from Health Score.
Project Achievements
Leaderboards
About
"ContainerSSH launches a new container for each SSH connection in Kubernetes or Docker. The user is transparently dropped in the container and the container is removed when the user disconnects. Authentication and container configuration are dynamic using webhooks, no system users required.
The main use cases for our present users are building labs and vendor access systems or debugging production systems with strict auditing, or running honeypots for security and academic research."
First commit
Software value
$4.5M
Maturity
Sandbox
License(s)
MIT-0
Apache-2.0
MIT
CC-BY-4.0
Other
Data sources
Git
GitHub
Hacker News