seriousm4x/UpSnap

A simple wake on lan web app written with SvelteKit, Go and PocketBase.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 10th, 2026
Created on November 16th, 2020
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 251
Total Stargazers: 6,271 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.5 hours
Mean response time: 3.4 days
90th percentile: 6.3 days
Tracked items: 47

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 8% of issues opened in the past year have been closed. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 69 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (45)
  • feature-request (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

upsnap is a web application for sending wake-on-LAN commands to devices on a network.

The tool solves the problem of remotely powering on computers without direct physical access or complex network administration. It combines a SvelteKit frontend with a Go backend and uses PocketBase as its database layer. Users can define devices in the system and trigger wake-on-LAN packets through a web interface, making it accessible from any browser on the network.

The project suits small networks or home lab environments where users want a straightforward way to manage device power states without deploying enterprise solutions. It is appropriate for anyone comfortable with self-hosting a web application and who has basic familiarity with network concepts like wake-on-LAN. The stack choice—SvelteKit for the frontend, Go for backend logic, and PocketBase for persistence—indicates a preference for simplicity and minimal operational overhead compared to heavier frameworks.

The codebase shows active maintenance with regular commits addressing bugs and adding features. The project accepts pull requests and responds to issues, indicating openness to community contributions. Development activity demonstrates consistent attention to the tool's core functionality rather than scope expansion.