reFlutter VS owasp-mstg

Compare reFlutter vs owasp-mstg and see what are their differences.

owasp-mstg

The Mobile Security Testing Guide (MSTG) is a comprehensive manual for mobile app security development, testing and reverse engineering. (by julepka)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
reFlutter owasp-mstg
6 1
1,460 0
- -
8.3 10.0
about 1 month ago almost 2 years ago
Python
GNU General Public License v3.0 only Creative Commons Attribution Share Alike 4.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

reFlutter

Posts with mentions or reviews of reFlutter. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-26.

owasp-mstg

Posts with mentions or reviews of owasp-mstg. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-03.
  • Google Play rolls out an "Independent security review" badge for apps
    2 projects | news.ycombinator.com | 3 Nov 2023
    I found a more detailed explanation of it: https://github.com/julepka/owasp-mstg/blob/master/Document/0...

    > Generally, you should provide compiled code with as little explanation as possible. Some metadata, such as debugging information, line numbers, and descriptive function or method names, make the binary or bytecode easier for the reverse engineer to understand, but these aren't needed in a release build and can therefore be safely omitted without impacting the app's functionality.

    I'm not a big fan of the reasoning, as it's security through obscurity. Which is not the worst tradeoff, but these days it just makes public bug bounties (and other public auditing) end up being less of an interesting prospect for improving security.

What are some alternatives?

When comparing reFlutter and owasp-mstg you can also consider the following projects:

apkleaks - Scanning APK file for URIs, endpoints & secrets.

buildAPKs - Really quickly build APKs on handheld device (smartphone or tablet) in Amazon, Android, Chromebook and Windows📲 See https://buildapks.github.io/docsBuildAPKs/setup to start building APKs.

MEDUZA - A more or less universal SSL unpinning tool for iOS

android-udev-rules - Android udev rules list aimed to be the most comprehensive on the net

owasp-mastg - The Mobile Application Security Testing Guide (MASTG) is a comprehensive manual for mobile app security testing and reverse engineering. It describes the technical processes for verifying the controls listed in the OWASP Mobile Application Security Verification Standard (MASVS).

website - The elementary.io website

awesome-security - A collection of awesome ethical hacking and security related content!

owasp-masvs - The OWASP MASVS (Mobile Application Security Verification Standard) is the industry standard for mobile app security.

disable-flutter-tls-verification - A Frida script that disables Flutter's TLS verification

theos-jailed - A Theos module to develop jailed tweaks for iOS 8 and up