spug

openspug/spug

Spug is a lightweight agent-free automatic operation and maintenance platform designed for small and medium-sized enterprises. It integrates host management, host batch execution, host online terminal, file management, application release and deployment, pipelines, online task planning, configuration center, monitoring, alarm and so on.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
7 Nov 2026
5 days ago
Ship score
78/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 11,084 → 11,103 (29 Sep – 10 Nov 2026)
+21 stars in the 28 days to 10 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
11.1K
Forks
2.2K
Open issues
10
Watchers
195
Primary language
JavaScript
Created
31 Jan 2018
Owner
openspug · 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. 59 startups in the directory ship primarily in JavaScript.

Topics

#alert#ci#cicd#cmdb#deploy#devops#django-ops#jenkins#monitor#operations#ops#ops-admin#ops-tools#opsadmin#spug#task#webconsole#webshell#webssh

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 92%, self-hostable 89%, hosted offering 51%. 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: shipping — last push 7 Nov 2026This is the badge for openspug/spug, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/openspug/spug.svg)](https://ossean.com/openspug/spug)

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.