Android security hardening — 4 low-risk fixes from audit
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, react-native, typescript
Research direction
Start with android/app/src/main/AndroidManifest.xml and src/screens/SettingsScreen.tsx, then inspect the production Babel config and the listed logging files. Check how the production Expo build handles SYSTEM_ALERT_WINDOW and console statements. Done means all four audit items are addressed and the production build and backup-import behavior are verified.
Written by the indexing model from the issue text.
Description
Context
A full security audit against the Android Security Best Practices checklist was performed on 2026-10-30. The app passes 44/48 checks. These 4 remaining items are all low-risk hardening improvements — no critical or high-risk issues were found.
The app's claim of being offline, privacy-first, and secure is substantiated by the audit.
[!NOTE]
This issue description was written by an AI agent (Antigravity / Claude Opus 4.6).
Checklist
1. Set android:allowBackup="false"
File: android/app/src/main/AndroidManifest.xml (L16)
Risk: LOW
android:allowBackup="true" allows full AsyncStorage data extraction via adb backup on Android ≤12. While the app stores no PII, users may type personal info into goal/camp names.
Fix: Set android:allowBackup="false", or define a restrictive android:fullBackupContent if Google Drive backup is desired.
2. Validate keys on backup import
File: src/screens/SettingsScreen.tsx (~L126-142)
Risk: LOW-MEDIUM
The import flow does JSON.parse() on user-supplied files and writes all entries to AsyncStorage via multiSet without validating key prefixes. A crafted backup file could inject arbitrary keys.
Fix: Filter incoming keys to known prefixes before writing:
const validPrefixes = ['@climbstack/', '@levelup/', 'app_language'];
const filteredEntries = backupData.data.filter(
([key]: [string, string]) => validPrefixes.some(p => key.startsWith(p))
);
await AsyncStorage.multiSet(filteredEntries);
3. Verify SYSTEM_ALERT_WINDOW is stripped from production builds
File: android/app/src/main/AndroidManifest.xml (L5)
Risk: LOW
This permission is declared in the main manifest (needed by React Native dev menu). Verify that eas build --profile production removes it. If not, move it to the debug-only manifest variant.
4. Strip console.log/error from production builds
Files: PeaksContext.tsx, PlannerContext.tsx, HomeScreen.tsx, calendar.ts, and others (~20 occurrences)
Risk: LOW
No PII is logged, but error objects in logcat could expose internal storage key names. Best practice is to strip console statements in production.
Fix: Add babel-plugin-transform-remove-console to the production Babel config, or wrap logs in __DEV__ checks.
AI Generation Disclosure
This issue was created by an AI agent (Antigravity, Claude Opus 4.6 Thinking). All files and line references were identified through automated codebase analysis.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GiZano/LevelUp
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·