> For the complete documentation index, see [llms.txt](https://developer.eagle.cool/plugin-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.eagle.cool/plugin-api/plugin-review/criteria.md).

# Review Criteria

This section explains what Eagle evaluates, which issues may block a submission, and how developers can prepare a compliant release.

{% hint style="warning" %}
Starting **July 21, 2026**, these criteria apply to all new plugin submissions and version updates.
{% endhint %}

{% hint style="info" %}
These criteria describe outcomes developers can observe and verify. Internal tools, detection methods, and decision thresholds are not published. Review coverage may change as security risks, platform capabilities, and policies evolve.
{% endhint %}

## Criteria and Review Stages

| Review area                                                                                                      | Primary stage | Focus                                                                         |
| ---------------------------------------------------------------------------------------------------------------- | ------------- | ----------------------------------------------------------------------------- |
| [Release Configuration and Reviewability](/plugin-api/plugin-review/criteria/configuration-and-reviewability.md) | Initial scan  | Package, `manifest.json`, release settings, and review information            |
| [Store Listing Copy](/plugin-api/plugin-review/criteria/store-listing-copy.md)                                   | Initial scan  | Name, description, introduction, changelog, locales, and material disclosures |
| [Visual Assets](/plugin-api/plugin-review/criteria/visual-assets.md)                                             | Initial scan  | Icon, covers, legibility, accuracy, and visual integrity                      |
| [Security and Privacy](/plugin-api/plugin-review/criteria/security-and-privacy.md)                               | Initial scan  | Dangerous behavior, external connections, data handling, and user awareness   |
| [Package Contents](/plugin-api/plugin-review/criteria/package-contents.md)                                       | Initial scan  | Sensitive files, development artifacts, nested archives, and binaries         |
| [File Safety](/plugin-api/plugin-review/criteria/file-safety.md)                                                 | Initial scan  | Malware, dangerous files, and a clean release build                           |
| [Functionality and Policy Compliance](/plugin-api/plugin-review/criteria/functionality-and-policy.md)            | Human review  | Installation, launch, main functionality, data changes, and policy compliance |

Only submissions that pass the initial scan proceed to human review. Human reviewers may revisit any item requiring context, so passing the first stage is not final approval.

## Blocking Issues and Recommendations

Review feedback distinguishes between:

* **Required changes:** Clear evidence shows that the submission violates a rule, is unsafe, materially misleads users, or cannot be reviewed as submitted. These issues block the current submission.
* **Non-blocking recommendations:** Optional quality improvements that do not affect safety, accuracy, or core use, such as minor grammar fixes or visual polish. These do not independently cause rejection.

When evidence remains unclear, the issue is evaluated in context or passed to human review. Uncertainty by itself is not treated as a violation.

## Before You Submit

Read every criterion relevant to your plugin, then use the [Prepare Plugin](/plugin-api/publishing/prepare.md) checklist. If the plugin uses external services, transfers data, runs system commands, includes binaries, or has special setup requirements, explain their purpose and provide test instructions.