mozilla/send

Simple, private file sharing from the makers of Firefox

Hosted by Mozilla

View on GitHub ↗Jump to charts ↓

mozilla/send has 13k+ stars and 1.5k+ forks on GitHub, is written in FreeMarker, and was last pushed on May 21, 2021. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 11 minutes ago
Added to GitGenius on October 12th, 2026
Created on May 22nd, 2017
Open Issues & Pull Requests: 156 (+0)
GitHub issues: Enabled
Number of forks: 1,629
Total Stargazers: 13,237 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
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

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Firefox Send is a file sharing application that enables encrypted transfer of files between users.

The tool addresses the need for private file exchange by implementing end-to-end encryption, allowing users to share files securely without exposing content to intermediaries. Files are encrypted on the client side before transmission, and recipients access them through a generated link. The service supports optional expiration times and download limits on shared files.

Developers considering this codebase should understand that Mozilla discontinued the Firefox Send service and the repository is archived. The source code remains available under the Mozilla Public License for forking and modification, but any deployment must remove all Mozilla and Firefox branding to comply with trademark policy and avoid confusing users about service ownership. The project requires Node.js and can optionally integrate Redis for caching and AWS S3 or compatible storage for file persistence. It includes comprehensive documentation covering encryption implementation, Docker deployment, build procedures, and metrics collection.

The project shows signs of maintenance activity through its test suite, linting and formatting tooling with prettier, and documented configuration via environment variables. Localization was managed through Pontoon rather than direct repository contributions, indicating structured community translation workflows. The codebase includes good first issues marked for new contributors and accepts pull requests, though the archived status means no active development occurs on the original service.