Transparency Scorecard Methodology

The directory believes open-source status and funding models are as important as the features a tool provides. To help with informed decisions, a Transparency Scorecard appears on every tool page.

This scorecard is not a review or an endorsement. It's a structured summary of factual, publicly available information regarding a project's governance and data practices.

How to read the scorecard

1. Open source

• ✓ YES: the full source code is available for inspection under an OSI-approved license.
• — NO: the software is proprietary or closed-source.
• — UNKNOWN: source availability could not be verified.

2. Account requirements

• ✓ NONE: the tool can be used without creating an account.
• • OPTIONAL: an account is available but not required for core functionality.
• REQUIRED: you must sign up (email, phone, etc.) to use the tool.

3. Telemetry and data collection

• ✓ NONE: the developers state they collect no usage data.
• • OPTIONAL: telemetry exists but is opt-in or easily disabled.
• — REQUIRED: the tool collects usage data that cannot be disabled.

4. Audits

• ✓ PASSED: the project has undergone a third-party security audit, and the report is public.
• • PARTIAL: specific components have been audited, but not the entire system.
• — NONE: no public audit reports were found.

5. Funding model

Understanding who pays for development is critical to understanding a tool's incentives. Funding is listed as subscriptions, donations, grants, or venture capital.

Disclaimer

Information is based on publicly available documentation and project disclosures at the time of writing. Projects change their policies frequently. Always verify critical claims yourself.