abhiabby3008/flutter-security-hardening-skill (flutter-security-hardening)

Audit and harden any Flutter app from TWO sources: (1) source code directory, or (2) built APK/XAPK file (from build folder, Downloads, any path, or ADB device). Source mode: scans code, finds vulnerabilities, scores 0-100, auto-fixes issues. APK mode: verifies the compiled binary — checks if obfuscation actually worked, extracts leaked secrets from libapp.so, validates manifest security flags, confirms SSL pinning, and compares source intentions vs binary reality. Trigger on: "secure my Flutter app", "protect from reverse engineering", "harden my app", "security audit Flutter", "protect API keys", "SSL pinning", "obfuscate Flutter", "protect my app data", "security best practices Flutter", "someone decompiled my app", "prevent APK tampering", "root detection Flutter", "flutter security", "protect secrets", "vulnerability scan", "check my APK", "audit my build", "is my APK secure", "verify my release build", "scan build/app/outputs", or any request about Flutter app security.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/abhiabby3008/flutter-security-hardening-skill

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.