dantheman827/ios-app-signer

This is an app for OS X that can (re)sign apps and bundle them into ipa files that are ready to be installed on an iOS device.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Type:ApplicationCategory(s):iOS & macOSMobile & Desktop
Added to GitGenius on September 17th, 2026
Created on November 6th, 2015
Open Issues & Pull Requests: 123 (+0)
GitHub issues: Enabled
Number of forks: 1,149
Total Stargazers: 6,317 (+0)
Total Subscribers: 206 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.3 hours
Mean response time: 37.4 days
90th percentile: 31.8 days
Tracked items: 14

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 422 days
Stale 30+ days: 14
Stale 90+ days: 14

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

No issue events were indexed in the last 7 days.

Detailed Description

ios-app-signer is a macOS application that resigns iOS apps and packages them into IPA files ready for device installation.

The tool addresses the need to modify and redeploy iOS applications by handling the code signing process, which is typically managed through Xcode. It allows developers to take existing app binaries, apply new signing certificates and provisioning profiles, and bundle them into installable IPA format without requiring the original source code or Xcode project setup.

This tool suits developers who need to resign apps for testing on physical devices, distribute internal builds, or work with precompiled binaries where source code access is limited or unnecessary. It is particularly useful for QA teams, beta testers, and developers managing multiple signing identities across different provisioning profiles. The graphical interface on macOS makes the signing process accessible without command-line expertise.

Development activity on the project is sparse, with infrequent commits and minimal recent engagement. The codebase remains in Objective-C, reflecting its age and lack of modernization to contemporary Swift standards. Issue responses and pull request activity are limited, suggesting the project receives minimal active maintenance or community support.