Devicon framework slug spelling and case-sensitivity affecting icon class resolution in locked environments

Devicon provides a CSS font delivering class-based icons for over two hundred programming languages and frameworks, intended as a consistent visual layer in documentation and dashboards. The mapping between framework names and icon classes follows a deterministic naming convention, yet it does not inherently account for framework version promotions or rebranding events, which can produce mismatches between the intended icon and the rendered glyph.

In repeatable development environments, practitioners often lock Devicon font assets to a specific version hash to stabilize CDN behavior, but the icon class name still requires an exact framework slug spelling and correct letter case. When a project adopts a renamed or versioned framework, the existing class may resolve to a default or missing glyph, undermining the consistency the font is designed to provide.

How does the Devicon mapping convention handle framework slugs that change due to official rebranding or major version bumps? What mechanism ensures icon class resolution remains consistent when a locked font version is paired with a framework whose naming convention has evolved? Is there a documented method to map frameworks current slug to its corresponding Devicon class without manual verification against the repository icon list?