Evaluate FiftyOne Plugins

Key Directives

ALWAYS follow these rules:

1. Read the entire plugin before judging

Read every source and configuration file of the plugin. Common file extensions: .py, .ts, .tsx, .js, .yaml, .yml, and .json. Never construct an assessment of a plugin without first reading every line of every source file.

2. Security first

Check for dangerous patterns before anything else. A plugin with perfect code quality that violates established and well known security best practices, is an immediate critical failure.

3. Be specific and actionable

Every finding must include: what's wrong, where it is (file + line), why it matters, and how to fix it. Never say "improve code quality" without pointing to the exact issue.

4. Score honestly

A plugin by a trusted org with security issues still gets a security failure. A community plugin with great code still gets credit. Judge the code, not the author.