notscuffed/repkg

Wallpaper engine PKG extractor/TEX to image converter

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 18th, 2026
Created on February 10th, 2019
Open Issues & Pull Requests: 20 (+0)
GitHub issues: Enabled
Number of forks: 298
Total Stargazers: 3,753 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 46.8 days
Mean response time: 129.5 days
90th percentile: 423.9 days
Tracked items: 24

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 618 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

RePKG is a command-line tool for extracting and converting Wallpaper Engine package files, written in C#.

Wallpaper Engine stores its assets in PKG container files and uses a proprietary TEX format for textures. RePKG solves the problem of accessing these assets by reverse-engineering both formats and providing extraction and conversion capabilities. The tool can extract PKG files to recover their contents, convert TEX texture files to standard image formats like PNG, and reconstruct complete Wallpaper Engine projects from PKG archives. It also supports dumping metadata about PKG and TEX files to inspect their structure.

The tool suits developers or enthusiasts who need to extract assets from Wallpaper Engine packages for analysis, archival, or repurposing. It works on individual files or batch-processes entire directory trees to find and convert multiple packages at once. Users can choose to extract only texture data as images, reconstruct full project structures, or simply inspect file information without extraction.

Development on the project is sparse, with infrequent commits and minimal recent activity. The maintainer has indicated openness to bug reports but does not appear to be actively developing new features or maintaining the codebase at a regular cadence.