Published
App Guidelines
Understand the quality, licensing, safety, and metadata expectations for OpenLib app listings.
OpenLib lists apps that are useful, understandable, and meaningfully open source.
Acceptance checklist #
- The source code is publicly accessible.
- The project uses an open-source license.
- The app has a real use case.
- Metadata is accurate and not promotional.
- Links point to official project resources.
- The app is not malware, deceptive software, or a clone intended to impersonate another project.
License expectations #
OpenLib prefers licenses recognized by open-source communities, such as MIT, Apache-2.0, GPL, LGPL, AGPL, MPL-2.0, BSD, and similar licenses.
Metadata quality #
Good listings are specific. Avoid vague descriptions like "best app ever" or "all-in-one tool." Explain what the app does, who it helps, and what it replaces.
Good: Open-source password manager with local vaults and browser extensions.
Weak: Amazing security app for everyone.Safety signals #
Maintainers may reject or unpublish apps when:
- Download links are suspicious or unrelated.
- The project distributes binaries without source parity.
- The app imitates another project in a confusing way.
- The repository contains malware reports that are not resolved.
Deprecation #
Apps can remain listed but marked deprecated when they are historically useful, replaced by a maintained fork, or no longer recommended for new users.
Contributors
- OpenLib Team