winsw/winsw

A wrapper executable that can run any executable as a Windows service, in a permissive license.

View on GitHub ↗Jump to charts ↓

winsw/winsw has 14k+ stars and 1.5k+ forks on GitHub, is written in C#, and was last pushed on Jul 30, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:CLI ToolCategory(s):CLI UtilitiesDeveloper Tools
Added to GitGenius on September 4th, 2026
Created on February 3rd, 2010
Open Issues & Pull Requests: 265 (+0)
GitHub issues: Enabled
Number of forks: 1,708
Total Stargazers: 14,371 (-1)
Total Subscribers: 220 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.5 days
Mean response time: 61.1 days
90th percentile: 80.9 days
Tracked items: 339

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 8% of issues opened in the past year have never received a reply. 94% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 89% of issues opened in the past year have been closed, leaving a working backlog. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 70
New in 7 days: 13
Closed in 7 days: 0
Avg open age: 584 days
Stale 30+ days: 41
Stale 90+ days: 40

Recent activity

Opened in 7 days: 12
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 11

Top labels

  • new-feature (213)
  • bug (80)
  • spam (80)
  • documentation (22)
  • good first issue (4)
  • help wanted (4)
  • build-flow (2)
  • discussion (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

WinSW is a wrapper executable that runs any application as a Windows service under a permissive license.

The tool solves the problem of managing arbitrary executables as Windows services without requiring custom service code. It works by wrapping the target application with an XML configuration file that specifies service metadata, startup behavior, and management options. Users rename the WinSW executable to match their application, place it alongside an XML config file, and use command-line operations to install, start, stop, and monitor the service.

WinSW suits developers and system administrators who need to run non-service applications as Windows services without modifying the application itself. It works well for legacy applications, scripts, or any executable that lacks native Windows service support. The tool is particularly useful in enterprise environments and CI/CD pipelines where service management is required. The project provides both .NET Framework and native .NET 7 executables to accommodate different Windows environments, from older systems with Framework 4.6.1 to modern Windows 10 and Server platforms.

The project maintains parallel development tracks with version 2.x receiving stable releases while version 3.x development occurs on the default branch. The tool is distributed through multiple channels including GitHub Releases, NuGet packages, Maven repositories via the Jenkins project, and Azure Pipelines CI builds. Documentation is comprehensive, covering XML configuration file specifications, command-line interface details, and practical samples for common use cases.