Published
Moderation Workflow
Learn how maintainers review submissions, edit requests, reports, reviews, and trust-sensitive changes.
Moderation keeps OpenLib useful and safe without blocking healthy community contributions.
What maintainers review #
Maintainers may review:
- New app submissions.
- Edit requests.
- Reports.
- Reviews.
- Ownership claims.
- Organization verification.
- Role applications.
- Deprecated or unsafe listings.
Review priorities #
Handle urgent trust and safety issues first.
- Reports involving malware, phishing, impersonation, or unsafe downloads.
- App restrictions or removals.
- Ownership claims and verification.
- New app submissions.
- Edit requests.
- Reviews and general cleanup.
Evidence-first decisions #
Every moderation decision should be based on evidence when possible.
Good evidence includes:
- Official repository.
- Project website.
- Release page.
- License file.
- Maintainer announcement.
- Security advisory.
- Verified organization or domain proof.
Decision outcomes #
| Outcome | Use when |
|---|---|
| Approve | The item is accurate and in scope |
| Request changes | The item is useful but incomplete |
| Reject | The item is inaccurate, unsupported, unsafe, or out of scope |
| Restrict | A listing may put users at risk |
| Remove | A listing should not remain public |
| Restore | A previous enforcement action was resolved or mistaken |
Moderation notes #
Leave notes when a decision may be questioned later. Notes should explain what was checked and why the action was taken.
Related docs #
Contributors
- OpenLib Team