Avoid Android world-readable or world-writable IO modes
Context files and shared preferences must not use MODE_WORLD_READABLE or MODE_WORLD_WRITABLE.
#Metadata
#Why it matters
Legacy Android modes expose application data to other packages on the device and break sandbox expectations for secrets.
#Remediation
Use MODE_PRIVATE or scoped storage APIs instead of world-readable or world-writable modes.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/java/java.security.android-world-readable-mode.rule.yaml.