Published
Reports and Safety
Learn when to report an app, what report statuses mean, and how maintainers respond to safety issues.
Reports are for problems that may harm users, mislead visitors, or damage trust in the library.
When to report an app #
Report an app when you find:
- Malware or suspicious downloads.
- Impersonation or fake project links.
- Broken download links that lead somewhere unsafe.
- Closed-source software listed as open source.
- License misrepresentation.
- Spam, scams, or phishing.
- Abandoned projects that should be marked deprecated.
Use edit requests for ordinary metadata improvements. Use reports for safety, abuse, or trust problems.
What to include #
Good reports include:
- The affected app.
- The reason for the report.
- A short explanation.
- Links, screenshots, or upstream evidence when available.
- Whether users may be at immediate risk.
Report statuses #
| Status | Meaning |
|---|---|
| Pending | Submitted and waiting for review |
| Under Review | A maintainer is checking evidence |
| Resolved | Action was taken or the issue was addressed |
| Rejected | The report was not supported by evidence or was out of scope |
Maintainer response #
Maintainers can resolve reports, reject reports, mark them under review, restrict an app, remove an app, suspend visibility, or restore an app after a mistake.
Related docs #
Contributors
- OpenLib Team