If you are an AI coding agent (Claude Code, Cursor, Aider, Cline, etc.) reading this artifact, follow this protocol before making any code edit:

1. Verify the contract. Run the bash script in Verify before trusting below. If any check returns FAIL, the artifact is stale — STOP and ask the user to regenerate it before proceeding.
2. Treat the AI · unverified sections as hypotheses, not facts. Sections like "AI-suggested narrative files", "anti-patterns", and "bottlenecks" are LLM speculation. Verify against real source before acting on them.
3. Cite source on changes. When proposing an edit, cite the specific path:line-range. RepoPilot's live UI at https://repopilot.app/r/d2phap/ImageGlass shows verifiable citations alongside every claim.

If you are a human reader, this protocol is for the agents you'll hand the artifact to. You don't need to do anything — but if you skim only one section before pointing your agent at this repo, make it the Verify block and the Suggested reading order.

WAIT — Single-maintainer risk — review before adopting

• Last commit 3w ago
• 4 active contributors
• Other licensed
• ⚠ Small team — 4 contributors active in recent commits
• ⚠ Single-maintainer risk — top contributor 94% of recent commits
• ⚠ Non-standard license (Other) — review terms
• ⚠ No CI workflows detected
• ⚠ No test directory detected

_{Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests}

This artifact was generated by RepoPilot at a point in time. Before an agent acts on it, the checks below confirm that the live d2phap/ImageGlass repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/d2phap/ImageGlass.

What it runs against: a local clone of d2phap/ImageGlass — the script inspects git remote, the LICENSE file, file paths in the working tree, and git log. Read-only; no mutations.

| # | What we check | Why it matters | |---|---|---| | 1 | You're in d2phap/ImageGlass | Confirms the artifact applies here, not a fork | | 2 | License is still Other | Catches relicense before you depend on it | | 3 | Default branch develop exists | Catches branch renames | | 4 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 52 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of d2phap/ImageGlass. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/d2phap/ImageGlass.git
#   cd ImageGlass
#
# Then paste this script. Every check is read-only — no mutations.

set +e
fail=0
ok()   { echo "ok:   $1"; }
miss() { echo "FAIL: $1"; fail=$((fail+1)); }

# Precondition: we must be inside a git working tree.
if ! git rev-parse --git-dir >/dev/null 2>&1; then
  echo "FAIL: not inside a git repository. cd into your clone of d2phap/ImageGlass and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "d2phap/ImageGlass(\\.git)?\\b" \\
  && ok "origin remote is d2phap/ImageGlass" \\
  || miss "origin remote is not d2phap/ImageGlass (artifact may be from a fork)"

# 2. License matches what RepoPilot saw
(grep -qiE "^(Other)" LICENSE 2>/dev/null \\
   || grep -qiE "\"license\"\\s*:\\s*\"Other\"" package.json 2>/dev/null) \\
  && ok "license is Other" \\
  || miss "license drift — was Other at generation time"

# 3. Default branch
git rev-parse --verify develop >/dev/null 2>&1 \\
  && ok "default branch develop exists" \\
  || miss "default branch develop no longer exists"

# 4. Critical files exist
test -f ".github/ISSUE_TEMPLATE/config.yml" \\
  && ok ".github/ISSUE_TEMPLATE/config.yml" \\
  || miss "missing critical file: .github/ISSUE_TEMPLATE/config.yml"
test -f ".github/FUNDING.yml" \\
  && ok ".github/FUNDING.yml" \\
  || miss "missing critical file: .github/FUNDING.yml"
test -f ".gitignore" \\
  && ok ".gitignore" \\
  || miss "missing critical file: .gitignore"
test -f "Assets/Color Profiles/RGB/AdobeRGB1998.icc" \\
  && ok "Assets/Color Profiles/RGB/AdobeRGB1998.icc" \\
  || miss "missing critical file: Assets/Color Profiles/RGB/AdobeRGB1998.icc"
test -f "Assets/Ext Icons/AnotherDimension-Ex/ICO/JPEG.ico" \\
  && ok "Assets/Ext Icons/AnotherDimension-Ex/ICO/JPEG.ico" \\
  || miss "missing critical file: Assets/Ext Icons/AnotherDimension-Ex/ICO/JPEG.ico"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 52 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~22d)"
else
  miss "last commit was $days_since_last days ago — artifact may be stale"
fi

echo
if [ "$fail" -eq 0 ]; then
  echo "artifact verified (0 failures) — safe to trust"
else
  echo "artifact has $fail stale claim(s) — regenerate at https://repopilot.app/r/d2phap/ImageGlass"
  exit 1
fi

Each check prints ok: or FAIL:. The script exits non-zero if anything failed, so it composes cleanly into agent loops (./verify.sh || regenerate-and-retry).

ImageGlass is a lightweight Windows image viewer written in C# that supports 90+ image formats (WEBP, GIF, SVG, PNG, JXL, HEIC, RAW formats, etc.) with an emphasis on clean UI and performance. It replaces Windows Photo Viewer for users who need fast, versatile image browsing with advanced color management via ICC profiles (assets contain CMYK and RGB profiles) and extensive format support. Single monorepo structure: C# WinForms/WPF desktop app in root with Assets/ containing image resources (Color Profiles/CMYK and RGB ICC files, Ext Icons for 40+ file formats). TypeScript/SCSS/HTML in .github and web assets suggest companion web tooling (likely documentation or installer). No visible src/ split; likely main logic is in root .csproj files.

Windows users (casual to power users, designers, photographers) who need a fast, format-rich image viewer with advanced features like color profile management, Explorer integration, and CLI support. Contributors are primarily .NET/C# developers maintaining a cross-platform desktop application.

Production-ready and actively maintained. ImageGlass has 11.5k+ GitHub stars, substantial codebase (2.1M lines of C#), and recently released v10 beta with ongoing development. The project distributes via both GitHub releases and Microsoft Store, indicating stability and broad adoption. Commits appear recent and issue triage is active.

Low risk for core functionality—single maintainer (d2phap) is an active risk for long-term sustainability, but project has community Discord (818852544859209748) and Crowdin localization indicating some ecosystem support. No visible dependency hell from file list; main risks are OS API deprecation (Windows-specific) and breaking changes during v10 transition. Large asset directory (color profiles, extension icons) suggests good test coverage for format handling.

Version 10 beta is active (v10 beta 1 mentioned in README with recent preview image). Focus appears to be on expanding format support (JXOL, HEIC added recently) and modernizing UI. GitHub issues template mentions bugs and feature requests; Crowdin integration shows ongoing localization effort across multiple languages.

Clone and open in Visual Studio 2022+ (inferred from C# 2.1M LOC and .NET stack): git clone https://github.com/d2phap/ImageGlass.git && cd ImageGlass. Look for .sln file and build with dotnet build or open in Visual Studio IDE. No npm/yarn needed; Windows-only build environment.

Daily commands: Clone repo, open .sln in Visual Studio 2022 or run dotnet build from root, then execute the compiled .exe. No dev server—native Windows app. Likely requires Windows 10+ and .NET 6.0+ runtime.

• .github/ISSUE_TEMPLATE/config.yml — Defines issue template configuration and contribution guidelines that shape how the project receives bug reports and feature requests.
• .github/FUNDING.yml — Specifies funding and sponsorship mechanisms critical for project sustainability and contributor recognition.
• .gitignore — Defines what files are excluded from version control; essential for understanding build artifacts, dependencies, and local configuration handling.
• Assets/Color Profiles/RGB/AdobeRGB1998.icc — Core color profile asset used by the image viewer's color management pipeline for accurate image rendering.
• Assets/Ext Icons/AnotherDimension-Ex/ICO/JPEG.ico — File extension icons that appear throughout the UI, representing the visual identity for supported image formats.
• .github/pull_request_template.md — Pull request template that standardizes contribution workflow and ensures quality of incoming changes.

• Format Manager (Icon asset files (.ico), extension registry) — Maps file extensions to supported image formats; retrieves and displays appropriate extension icons from the Assets/Ext Icons collection.
  • Failure mode: Unsupported format → display generic icon; missing icon asset → fallback to default image icon.
• Color Management System (ICC profile files, color transformation engine) — Selects and applies ICC color profiles (RGB or CMYK) to ensure accurate image rendering across display and print workflows.
  • Failure mode: Missing color profile → use default sRGB; corrupted profile → revert to unmanaged color rendering.
• Image Renderer (Format decoders, color profile lookup, graphics rendering API) — Decodes image pixel data and applies color transformations before display; handles all 90+ supported formats.
  • Failure mode: Unsupported codec → error dialog; memory exhaustion on large files → user prompted or image downsampled.
• UI/Icon Layer (AnotherDimension-Ex icon set, UI framework) — Displays file icons in file browsers and tabs; provides visual feedback for image format types.
  • Failure mode: Missing icon asset → fallback to generic file icon; icon render failure → blank placeholder.

• File System → Format Manager — User selects or drags image file; extension is extracted and matched against supported format registry.
• Format Manager → Image Renderer — Validated format triggers appropriate decoder selection; image bytes are streamed to renderer.
• Image Renderer → Color Manager — Renderer queries color space metadata from image (e.g., embedded ICC profile or color space tag) and requests matching profile.
• Color Manager → Asset Store (Assets/Color Profiles/) — Profile lookup loads .icc file from RGB/ or CMYK/ subfolder and passes transformation matrix to renderer.
• Image Renderer → UI/Display — Color-corrected pixel data is rendered to screen; file icon is looked up from Assets/Ext Icons/ and displayed in UI.
• Issue/PR Template → GitHub Issue/PR Creation — User fills template from .github/ISSUE_TEMPLATE/ directory; structured data improves triage and developer communication.

Add Support for a New Image Format

1. Create a new .ico file in Assets/Ext Icons/AnotherDimension-Ex/ICO/ following the naming convention (FORMATNAME.ico) (Assets/Ext Icons/AnotherDimension-Ex/ICO/)
2. Create the corresponding .psd source file in Assets/Ext Icons/AnotherDimension-Ex/PSD/ for future design modifications (Assets/Ext Icons/AnotherDimension-Ex/PSD/)
3. Update the image format registry in the core viewer code to recognize the new extension and map it to its icon asset ([core viewer codebase - not visible in file list])

Add Color Profile Support for a New Standard

1. Place the ICC color profile file (.icc) in the appropriate subfolder: Assets/Color Profiles/RGB/ for RGB or Assets/Color Profiles/CMYK/ for CMYK (Assets/Color Profiles/)
2. Register the profile path in the color management configuration module to make it available to the rendering pipeline ([core viewer codebase - not visible in file list])

Update Issue/PR Templates for New Contribution Workflow

1. Edit the relevant template file in .github/ISSUE_TEMPLATE/ (e.g., 01-bug.yml, 02-feature-request.yml) to add or modify required fields (.github/ISSUE_TEMPLATE/)
2. Update .github/pull_request_template.md to reflect any new checklist items or contribution requirements (.github/pull_request_template.md)
3. Review .github/ISSUE_TEMPLATE/config.yml to verify the template routing and help text are correctly configured (.github/ISSUE_TEMPLATE/config.yml)

• ICC Color Profiles (.icc files) — Essential for professional-grade color accuracy across CMYK and RGB color spaces; supports industry-standard print and display standards.
• File Extension Icons (AnotherDimension-Ex set) — Provides visual differentiation for 90+ supported image formats; improves UX by making file types instantly recognizable in the UI.
• GitHub Issues/PR Templates — Standardizes contribution quality and ensures bug reports include reproducible steps; reduces maintenance overhead and improves issue triaging.

• Bundling 90+ file extension icons in the repository

  • Why: Enables offline availability and guaranteed icon consistency with the viewer release.
  • Consequence: Increases repository size and build artifact footprint; requires manual updates when new formats are added.

• Including color profiles for multiple print standards (FOGRA, Japan Color, SWOP)

  • Why: Supports global professional workflows without requiring users to manually install profiles.
  • Consequence: Adds asset weight and complicates color management configuration; may confuse users with many profile choices.

• Lightweight image viewer design (inferred from README)

  • Why: Targets users wanting fast, responsive image browsing without bloated features.
  • Consequence: May lack advanced editing or batch-processing features; positioned as viewer-only, not editor.

• Does not provide image editing capabilities (crop, filter, transform)
• Does not handle authentication or cloud storage integration
• Not a batch image processing or conversion tool
• Does not include advanced metadata editing beyond EXIF viewing
• Not a real-time collaborative tool

• Hardcoded Icon Asset Paths (Medium) — Assets/Ext Icons/AnotherDimension-Ex/ICO/ (inferred usage in viewer core): If format-to-icon mappings are hardcoded in the main viewer code rather than using a registry or configuration file, adding new formats requires code changes instead of simple asset additions.
• Incomplete Color Profile Coverage (Low) — Assets/Color Profiles/ (missing profiles): If users frequently encounter images in color spaces not covered by bundled profiles (e.g., Lab, DCI-P3, Rec. 2020), the viewer falls back to poor color management.
• No Profile Validation at Build Time (Medium) — Assets/Color Profiles/: ICC profile files are not validated during the build process; corrupted or malformed .icc files could cause runtime failures only when users select that profile.

• undefined (undefined) — undefined

Windows-only: entire codebase is Windows desktop (WinForms/WPF); cross-platform builds will fail. ICC profile path assumptions: Color Profiles must be deployed with app or embedded in resources; missing profiles silently degrades color accuracy. Explorer integration: file type association via registry; requires admin on fresh install. Format decoder dependencies: exotic formats (JXL, HEIC) may require specific codec libraries (libjxl, HEIF library) as native dependencies—check build scripts. v10 migration: breaking changes from v9 may affect plugins/extensions; check migration guide if extending.

• ICC Color Profiles — ImageGlass bundles 22 ICC profiles (CMYK, RGB variants) to handle professional color-managed workflows; understanding color space conversion (sRGB → AdobeRGB → CMYK) is essential to this app's value
• Windows Picture Format (WIC) / GDI+ — Core Windows APIs for image decoding; ImageGlass likely uses WIC for native formats and wraps third-party decoders for exotic ones
• File Type Associations via Registry — ImageGlass integrates into Explorer context menu; requires HKEY_CLASSES_ROOT registry edits, shell verb registration, and correct CLSID handling on install
• RAW Codec Support — App supports 40+ camera RAW formats (CR2, ARW, DNG, etc.); requires either Windows Camera Codec Pack, WIC extensions, or bundled native decoders
• Icon Resources (.ico) Bundling — Assets/Ext Icons/ contains 100+ .ico files for format detection; proper icon registration improves Explorer UX and sets ImageGlass apart from generic viewers
• MSIX/AppX Packaging — Distributes via Microsoft Store as MSIX; requires understanding app signing, capability declarations, and sandboxing constraints vs classic .exe
• Drag-and-Drop File Handling — Core UX pattern in image viewers; WinForms/WPF implementation must handle multiple file types, folder drops, and async loading without blocking UI

• faststone/FastStone-Image-Viewer — Direct alternative image viewer for Windows with similar lightweight philosophy; if FastStone were open-source, would be main competitor
• nomacs/nomacs — Open-source cross-platform image viewer (C++) with color management; shows different architecture approach (Qt instead of WPF)
• ShareX/ShareX — Windows screenshot/screen recording tool with image annotation; shares WinForms/C# stack and Explorer integration patterns
• ImageMagick/ImageMagick — Command-line image processing engine; ImageGlass likely wraps or uses equivalent codecs for format handling
• libjxl/libjxl — JPEG XL codec library; ImageGlass supports JXL format, likely uses this decoder under the hood

To work on one of these in Claude Code or Cursor, paste: Implement the "<title>" PR idea from CLAUDE.md, working through the checklist as the task list.

Add CI/CD workflow for color profile validation and ICC file testing

The repo contains 14+ ICC color profile files (CMYK and RGB) in Assets/Color Profiles/ but there's no automated validation that these files are valid, not corrupted, and properly formatted. A GitHub Action could validate ICC profile integrity on every commit, preventing accidental corruption of these critical assets that affect image rendering accuracy.

• [ ] Create .github/workflows/validate-color-profiles.yml workflow
• [ ] Add a validation script (e.g., in Python or C#) that checks ICC file headers and structure integrity
• [ ] Test against all files in Assets/Color Profiles/CMYK/ and Assets/Color Profiles/RGB/
• [ ] Fail the workflow if any profile is invalid or corrupted
• [ ] Document the validation approach in CONTRIBUTING.md

Create asset inventory system and CI check for extension icon completeness

The Assets/Ext Icons/AnotherDimension-Ex/ICO/ directory contains 50+ file format icons but there's no validation ensuring all supported image formats have corresponding icons, or that newly supported formats get icons added. A contributor could build a registry mapping supported formats to their icons and enforce it in CI.

• [ ] Create a JSON/YAML manifest file listing all supported image formats and their icon file requirements
• [ ] Add a validation script that checks if every format in the manifest has a corresponding .ico file
• [ ] Integrate this check into a GitHub Action (e.g., .github/workflows/validate-icons.yml)
• [ ] Update any format support lists to reference this manifest
• [ ] Document how to add icons for new formats in CONTRIBUTING.md

Add GitHub Action workflow for localization file synchronization with Crowdin

The README references Crowdin for localization (indicated by the incomplete Crowdin badge URL), but there's no visible automation ensuring translations stay in sync with the codebase. A new contributor could set up a workflow that syncs source strings to Crowdin and imports completed translations back into the repo on a schedule or trigger.

• [ ] Create .github/workflows/crowdin-sync.yml workflow file
• [ ] Configure Crowdin API integration using repository secrets for API token
• [ ] Add steps to upload source language strings (identify where these are defined in the codebase)
• [ ] Add steps to download completed translations back to the appropriate directory
• [ ] Set up scheduled runs (e.g., daily or on release) and manual trigger option
• [ ] Document the translation workflow in CONTRIBUTING.md

• Add AVIF codec support to format list: extend Assets/Ext Icons/ with AVIF.ico and document decoder integration path—high visibility, helps users on modern web
• Create test coverage for color profile loading: write unit tests for ICC profile parsing (CMYK/RGB files in Assets/) to catch profile corruption—currently no visible test directory
• Document Explorer sort order preservation feature in /docs: README mentions "Explorer sort order" as differentiator vs Store version but no user guide—good docs PR for new contributors

ImageGlass appears to be a desktop image viewer application with a reasonable security posture based on available information. No critical vulnerabilities were identified in the visible file structure. However, the analysis is limited due to missing dependency manifests and source code files. Key areas for improvement include: (1) providing dependency manifests for automated vulnerability scanning, (2) strengthening the security disclosure policy with clear contact information, and (3) ensuring regular dependency updates are applied. The codebase follows good practices by maintaining a SECURITY.md file and using version-based support policies. For a complete security assessment, review of actual source code for injection vulnerabilities, input validation, and secure file handling would be necessary.

• Medium · Incomplete Security Policy — SECURITY.md. The SECURITY.md file indicates that versions ≤ 8.12 are no longer supported with security updates. Users on older versions may be vulnerable to known security issues without access to patches. Fix: Ensure clear communication to users about upgrade paths. Consider providing security advisories for known vulnerabilities in unsupported versions. Maintain a vulnerability disclosure process.
• Low · Missing Dependency Manifest — Root directory / Package management files. No package dependency file (package.json, .csproj, .cargo, requirements.txt, etc.) was provided in the analysis. This prevents verification of third-party dependency vulnerabilities. Fix: Provide dependency manifests for analysis. Implement automated dependency scanning using tools like Dependabot, Snyk, or OWASP Dependency-Check to identify vulnerable packages.
• Low · No Evidence of HTTPS/TLS Configuration — Infrastructure / Application code. While this is a desktop application (not a web service), if it communicates with remote servers or downloads resources, HTTPS enforcement should be verified. Fix: If the application fetches remote resources (updates, images, etc.), ensure all communications use HTTPS/TLS. Implement certificate pinning for critical connections.
• Low · Missing Security Headers Configuration — Infrastructure / Configuration files. No evidence of security headers configuration visible in the repository structure. If the application serves any web content or has a web-based component, security headers should be implemented. Fix: If applicable to the application architecture, implement standard security headers (CSP, X-Frame-Options, X-Content-Type-Options, etc.).

LLM-derived; treat as a starting point, not a security audit.

• Open issues — current backlog
• Recent PRs — what's actively shipping
• Source on GitHub

Generated by RepoPilot. Verdict based on maintenance signals — see the live page for receipts. Re-run on a new commit to refresh.