uvdesk/community-skeleton

community-skeleton

uvdesk · Organization · CSS

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

Snapshot of 2026-08-11 · 598 repos · every number on this page is measured against that date.

Ship status

Gone silent

No verified push in over 120 days. A quiet repo may also be a finished one.

Last verified push
Oct 1, 2025
Days since that push
314 days before this snapshot
Ship score
10 / 100 how it is calculated →

Thresholds: ≤30 days shipping · 31120 slowed · >120 silent · unreachable for 3 days unverified.

Measured against the snapshot of 2026-08-11, not against today.

How we measure →

Repo facts

What the snapshot recorded.

Stars

19.5K

Snapshot of 2026-08-11

Forks

563

Snapshot of 2026-08-11

Open issues

78

Issues and pull requests GitHub reports as open

Watchers

47

Accounts subscribed to the repository

Primary language

CSS

1 startup in the directory ship primarily in CSS.

License

Open Software License 3.0

OSI-approved license. GitHub's own license field, not legal advice.

Created

Nov 2, 2018

Repository creation date on GitHub

Owner

uvdesk · Organization

Last verified push Oct 1, 2025

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

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last verified push 2025-10-01This is the live badge for uvdesk/community-skeleton, served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/uvdesk/community-skeleton.svg)](https://ossean.com/uvdesk/community-skeleton)

Updates daily. It shows the last verified push — how we measure it.

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.