deepfakes/faceswap

Deepfakes Software For All

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on August 31st, 2026
Created on December 19th, 2017
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 13,487
Total Stargazers: 57,520 (+0)
Total Subscribers: 1,522 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 days
Mean response time: 138.7 days
90th percentile: 534.5 days
Tracked items: 64

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

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 (2)
  • AppleSilicon (1)
  • code to integrate (1)
  • docker (1)
  • feature (1)
  • suggestion (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

FaceSwap is a tool that utilizes deep learning to recognize and swap faces in pictures and videos. It employs neural networks trained to detect facial features and perform face replacement across image and video content. The tool operates through a pipeline of extract, train, and convert stages, where faces are first identified and isolated, a model is trained on source and destination faces, and finally the trained model is applied to generate the swapped output.

The project is designed for users interested in face-swapping applications, from hobbyists experimenting with the technology to those building on generative models. It provides both command-line and graphical interfaces to make the workflow accessible to non-developers. The README emphasizes that FaceSwap has ethical uses and includes a manifesto addressing this concern, indicating the maintainers are conscious of the tool's potential for misuse.

Development activity shows a typical response time of one to two weeks for initial engagement with issues and pull requests. Work in the issue tracker centers on bug fixes, Docker-related improvements, and feature requests, suggesting the project maintains focus on stability, containerization support, and incremental capability expansion.