community-skeleton

uvdesk/community-skeleton

UVdesk Open Source Community Helpdesk is a comprehensive ticketing support system designed for everyone, offering robust features to streamline customer support and collaboration.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
7 Oct 2026
40 days ago
Ship score
40/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 19,625 → 19,644 (6 Oct – 17 Nov 2026)
+7 stars in the 28 days to 17 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
19.6K
Forks
560
Open issues
84
Watchers
46
Primary language
CSS
License
Open Software License 3.0
Created
2 Nov 2018
Owner
uvdesk · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 1 startup in the directory ships primarily in CSS.

Topics

#agent-privilege#backbonejs#customer-support#docker-runtime#ecommerce-apps#ecommerce-apps-integration#freshdesk-alternative#knowledgebase#mailboxes#opensource#osticket-alternative#support-tickets#symfony4#ticketing-system#uvdesk#uvdesk-community#workflows#zendesk-alternative

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 88%, self-hostable 78%, hosted offering 74%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 7 Oct 2026This is the badge for uvdesk/community-skeleton, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/uvdesk/community-skeleton.svg)](https://ossean.com/uvdesk/community-skeleton)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.