Use this register to find the source, then inspect the source directly before installing or updating software.
Every consequential claim leaves a trail.
This register separates primary project evidence from community reports and adjacent-tool context. Nothing here is presented as a live feed.
Evidence before persuasion.
The auditable record.
Official project
09 SOURCES- Original Forge repository and README
Definition, project goals, features, installation and repository identity.
- Forge UI construction code
Exact labels for presets, checkpoint, low bits, swap and GPU weights.
- Original Forge latest release
Windows archive destination, asset variants and dates.
- GitHub repository metadata API
Archived state, license and last push timestamp.
- GitHub release metadata API
Asset upload dates and absent digest fields.
- Forge license
AGPL-3.0 license identity.
- Gradio 4 / Forge Canvas announcement
Canvas behavior and dated extension-compatibility context.
- Flux / BitsandBytes guide
Low-bit and model-path terminology.
- Performance reporting guidance
Why controlled evidence is required for speed and memory claims.
Upstream
01 SOURCES- AUTOMATIC1111 Stable Diffusion WebUI
Inherited WebUI workflow and feature baseline.
Community & regional
03 SOURCES- Linux install issue #138
Evidence of community paths and official-documentation gaps.
- 2025 WebUI comparison discussion
Familiarity, workflow fit and community perception.
- 2026 category-state discussion
Fork and project-state confusion.
Adjacent tools
04 SOURCES- Comfy
Node-graph workflow positioning.
- Fooocus repository
Simplified workflow and source-provenance warning.
- InvokeAI
Canvas-first creative workflow positioning.
- Stability Matrix
Multi-UI installation and shared-model management.
Technical
02 SOURCES- Astro 7.2 release
Static frontend framework selection.
- Node.js release schedule
Recommended build runtime.
What this evidence does not authorize.
The domain and guide are assumed independent unless written authorization is established.
Current GitHub release metadata exposes no digest for the inspected assets.
Results vary by model, architecture, precision, GPU, configuration and commit.
“Not archived” and old activity dates must remain visible together.