Review Criteria

Review the criteria used during the initial scan and human review of Eagle plugins.

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

Starting July 21, 2026, these criteria apply to all new plugin submissions and version updates.

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.

Criteria and Review Stages

Review area	Primary stage	Focus
Release Configuration and Reviewability	Initial scan	Package, manifest.json, release settings, and review information
Store Listing Copy	Initial scan	Name, description, introduction, changelog, locales, and material disclosures
Visual Assets	Initial scan	Icon, covers, legibility, accuracy, and visual integrity
Security and Privacy	Initial scan	Dangerous behavior, external connections, data handling, and user awareness
Package Contents	Initial scan	Sensitive files, development artifacts, nested archives, and binaries
File Safety	Initial scan	Malware, dangerous files, and a clean release build
Functionality and Policy Compliance	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 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.