Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Corrupt-delete file

Open
#4,721 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
android, kotlin
Domain
mobile, security

Research direction

The issue names no files, tests, or entry points. Start by locating the current file-delete flow in the Android app, then investigate storage targets and platform limitations before defining acceptance tests for overwriting followed by deletion.

Written by the indexing model from the issue text.

Description

Area-FileOperations help wanted Issue-Feature

Is your feature request related to a problem? Please describe.
To delete files in a non-recoverable way. You sure can delete a file, but it just gets marked as re-writable.

Describe the solution you'd like

A delete-feature that consists in injecting in the soon-to-be-deleted file random text in it, and then delete. Corrupt-delete

Describe alternatives you've considered
none

Additional context
In this way the file that get deleted is lost forever, corrupted.

Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 17h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TeamAmaze/AmazeFileManager

All issues in TeamAmaze/AmazeFileManager

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.