You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #697 introduced a new core library based on Shuriken-Analyzer, alongside a comparison with the existing Androguard-based one.
The comparison shows that both core libraries produce identical Quark reports when tested with the built-in rules and samples from apk-samples. Also, the information extracted by the new core library matches 99.84% on average with that extracted by the Androguard-based one.
Based on those results, I propose changing Quark's default core library to the Shuriken-based one.
How
Change the default value of the CLI flag --core-library to shuriken. However, to ensure all Quark features and the downstream tools remain functional, we should do the following checks before making this change.
Ensure Quark passes the unit tests and the smoke tests on Linux, macOS, and Windows platforms.
Ensure Quark Agent, Quark-Script, and Quark Report showcase work as expected.
Ensure Quark is installable via Pip, Pipenv, Kali Package, and Docker Image.
Ensure the integrations with IntelOwl, Jadx, MobSF, and Apklab work as expected.
Why
PR #697 introduced a new core library based on Shuriken-Analyzer, alongside a comparison with the existing Androguard-based one.
The comparison shows that both core libraries produce identical Quark reports when tested with the built-in rules and samples from apk-samples. Also, the information extracted by the new core library matches 99.84% on average with that extracted by the Androguard-based one.
Based on those results, I propose changing Quark's default core library to the Shuriken-based one.
How
Change the default value of the CLI flag
--core-librarytoshuriken. However, to ensure all Quark features and the downstream tools remain functional, we should do the following checks before making this change.