This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Release Preflight
Check release files for secrets before you ship
Release Preflight is a Mac app that checks folders, ZIPs, macOS apps, and Xcode archives before you ship. It flags possible exposed secrets, sensitive files, and debug settings, and helps you review Apple entitlements. Export findings as HTML or JSON. Scans run on your Mac, with optional OSV lookups for known advisories for exact versions of supported dependencies. Requires macOS 14 or later.
Hi Product Hunt, I'm Yuichi, the developer behind Release Preflight.
I built it for the last check before sharing a build. A folder or archive can still contain a test key or a development setting even when the build itself works. I wanted a way to check the files I was about to send.
Choose a folder, ZIP, macOS app, or Xcode archive and the app shows what it flagged, why it matters, and what you can check next. It masks detected secret values, leaves your files intact, and exports HTML or JSON if you want a record of the scan.
The checks cover common patterns. You can also enable an OSV lookup for known advisories for exact versions of supported dependencies. That lookup is off by default, and your source files stay on your Mac.
If you ship software from a Mac, what do you still check by hand just before you send a build?
About Release Preflight on Product Hunt
“Check release files for secrets before you ship”
Release Preflight was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #425 on the daily leaderboard. Release Preflight is a Mac app that checks folders, ZIPs, macOS apps, and Xcode archives before you ship. It flags possible exposed secrets, sensitive files, and debug settings, and helps you review Apple entitlements. Export findings as HTML or JSON. Scans run on your Mac, with optional OSV lookups for known advisories for exact versions of supported dependencies. Requires macOS 14 or later.
On the analytics side, Release Preflight competes within Mac, Developer Tools, GitHub and Security — topics that collectively have 671.5k followers on Product Hunt. The dashboard above tracks how Release Preflight performed against the three products that launched closest to it on the same day.
Who hunted Release Preflight?
Release Preflight was hunted by Yuichi Chiba. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Release Preflight including community comment highlights and product details, visit the product overview.
Yuichi Chiba
Hi Product Hunt, I'm Yuichi, the developer behind Release Preflight.
I built it for the last check before sharing a build. A folder or archive can still contain a test key or a development setting even when the build itself works. I wanted a way to check the files I was about to send.
Choose a folder, ZIP, macOS app, or Xcode archive and the app shows what it flagged, why it matters, and what you can check next. It masks detected secret values, leaves your files intact, and exports HTML or JSON if you want a record of the scan.
The checks cover common patterns. You can also enable an OSV lookup for known advisories for exact versions of supported dependencies. That lookup is off by default, and your source files stay on your Mac.
If you ship software from a Mac, what do you still check by hand just before you send a build?