[IT-1E8] Inspect the published Windows ZIP and Android APK
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Read the ## 1E8 section of the linked item file, then download the newest Windows ZIP from Lightning-downloads and the newest app APK into separate empty scratchpad folders. List each archive, check for the named sensitive files and paths, scan binaries with the patterns from 1E7, and compare APK permissions with packaging/android-permissions.txt. Record the checked versions and findings; if adding a release check, use tools/release_check.py and tests/test_release_check.py and run the specified pytest command.
Written by the indexing model from the issue text.
Description
Step IT-1E8 of #543 · design and history
Do:
Files: none changed; the newest release's ZIP from Lightning-downloads and the APK from the app's newest release, downloaded into their own empty scratchpad folder.
Do: list each archive (unzip -l); fail on any .git/, tests/, *.db/*.sqlite, recovery.txt, keys.json, *.pem/*.key/*.jks/*.p12, .env, a Documents/Lightning path or a name from the sample households outside lightning/samples/; run strings over the binaries for the patterns of 1E7; compare the APK's permissions (aapt dump permissions or apkanalyzer) with packaging/android-permissions.txt. If a check belongs in every release, add it to tools/release_check.py with a test in tests/test_release_check.py (create it if missing) in its own pull request.
Done when: this file has one dated line naming the two versions checked and "N findings filed privately"; any new release check passes python -m pytest tests/test_release_check.py -q.
Can: opus
Blocked by: none
Read: the section ## 1E8 of the item file above
Generated by Claude Code
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 364
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- 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 LightningEg/Lightning
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
LightningEg/Lightning#591 ·
Maintainers usually reply within 1 day
-
can:opus pillar:reach state:ready when:someday
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
LightningEg/Lightning#576 ·
Maintainers usually reply within 1 day
-
coins:200 good first issue kind:improvement-visual pillar:feel
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LightningEg/Lightning#435 ·
Maintainers usually reply within 1 day
-
coins:200 good first issue kind:improvement-visual pillar:feel
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LightningEg/Lightning#428 ·
Maintainers usually reply within 1 day
-
coins:200 good first issue kind:improvement-visual pillar:feel
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LightningEg/Lightning#426 ·
Maintainers usually reply within 1 day
All issues in LightningEg/Lightning
Similar issues
-
release
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MichaelYcJo/SpecSeal#1535 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
valentinfrlch/ha-llmvision#769 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
daniel-ospina/tortoise#11937 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue help wanted python up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
andrewsiah/agentswarm-data-tasks#238 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cadence-workflow/cadence-ai-samples#175 ·
Maintainers usually reply within 1 day