Control a separately installed application icon normalization backend. Provides status, automatic maintenance controls and preferences.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
EGO-M-004 error
metadata shell-version must only include plausible stable releases and at most one development release
Field `shell-version` contains invalid values, more than one development release, or implausible future releases.
metadata.json must be well-formed
Icon Normalizer
metadata.json
shell-version=['51']
| Version | Status |
|---|---|
| 1.1.8 (5) | Unreviewed |
| 1.1.2 (4) | Rejected |
| 1.1.1 (3) | Rejected |
| 1.1.1 (2) | Rejected |
| 1.1.1 (1) | Rejected |
Hello reviewers, Could you please advise whether any additional information or changes are needed to proceed with the review of this pending submission? I understand this is volunteer work and appreciate your time. The page currently lists only the experimental EGO-M-004 finding for shell-version ["51"]. GNOME 51 was officially released on September 16, 2026, and this extension was tested on GNOME Shell 51.0: https://release.gnome.org/51/ . Please consider whether this finding is a false positive. I have not added untested Shell versions to bypass the check. The current GitHub release is extension 1.1.2 with companion backend 3.1.1: https://github.com/TengJoe/icon-normalizer-plugin/releases/tag/v1.1.2 . The frontend JavaScript is unchanged; the new companion fixes per-icon rules, stale-source previews and applied-revision status. I am preparing the matching 1.1.2 website upload; it has not been uploaded yet. For clarity, the ZIP contains GJS frontend source and assets only, without Python modules, executable binaries, compiled schemas, installers, downloads or telemetry. The GPL-3.0-or-later companion is installed separately through explicit user action, uses user-level maintenance units with visible controls, and isolates image processing from Shell/GTK 4 preferences. The extension does not install the companion or request root access. Would you please let me know if the separate-companion architecture needs further justification or changes for acceptance? Its scope and validation limits are documented here: https://github.com/TengJoe/icon-normalizer-plugin/blob/v1.1.2/docs/SUBMISSION.md . Thank you.