Anchors
| Anchor text | Ref. domains ▾ | Top DR | Ref. pages | Links to target | Dofollow links |
|---|---|---|---|---|---|
| Várias chamadas para __del__ durante a destruição de objetos | 1 | — | 0 | 2 | 2 100% |
| Missing Dispose call on local IDisposable | 1 | — | 0 | 7 | 7 100% |
| 사용자가 제공한 배열 인덱스의 잘못된 유효성 검사 | 1 | — | 0 | 1 | 1 100% |
| https://codeql.github.com | 1 | — | 0 | 1 | 1 100% |
| Caractère passé au constructeur StringBuilder | 1 | — | 0 | 2 | 2 100% |
| Expression régulière mal ancrée | 1 | — | 0 | 2 | 2 100% |
| Certificat non vérifié | 1 | — | 0 | 2 | 2 100% |
| Verwendung konstanter Salts | 1 | — | 0 | 6 | 6 100% |
| Cross-site scripting armazenado | 1 | — | 0 | 8 | 8 100% |
| Cross-window communication with unrestricted target origin | 1 | — | 0 | 10 | 10 100% |
| Unsigned difference expression compared to zero | 1 | — | 0 | 24 | 24 100% |
| Uso de um algoritmo de hash criptográfico inadequado em senhas | 1 | — | 0 | 5 | 5 100% |
| Слабая конфигурация файлов cookie | 1 | — | 0 | 7 | 7 100% |
| Неполная проверка схемы URL-адресов | 1 | — | 0 | 2 | 2 100% |
| Trait de soulignement utilisé comme identificateur | 1 | — | 0 | 1 | 1 100% |
| Declaração de nome de método suspeito | 1 | — | 0 | 1 | 1 100% |
| O módulo importa a si mesmo | 1 | — | 0 | 2 | 2 100% |
| Test de comparaison inutile | 1 | — | 0 | 1 | 1 100% |
| SARIF | 1 | — | 0 | 22 | 22 100% |
| Включение функций из ненадежного источника | 1 | — | 0 | 2 | 2 100% |
| Creating an ASP.NET debug binary may reveal sensitive information | 1 | — | 0 | 38 | 38 100% |
| Off-by-one comparison against length | 1 | — | 0 | 17 | 17 100% |
| 不受控命令行 | 1 | — | 0 | 6 | 6 100% |
| Metadaten für CodeQL Abfragen | 1 | — | 0 | 3 | 3 100% |
| memset-Anruf könnte gelöscht werden | 1 | — | 0 | 6 | 6 100% |
| A chamada para 'System.IO.Path.Combine' pode remover silenciosamente seus argumentos anteriores | 1 | — | 0 | 1 | 1 100% |
| Remote property injection | 1 | — | 0 | 10 | 10 100% |
| Illegal invocation | 1 | — | 0 | 9 | 9 100% |
| 두 번 컴파일 | 1 | — | 0 | 3 | 3 100% |
| XPath 삽입 | 1 | — | 0 | 4 | 4 100% |
| 메모리 액세스 함수에 대한 호출은 버퍼를 오버플로할 수 있습니다. | 1 | — | 0 | 3 | 3 100% |
| Imprecise assert | 1 | — | 0 | 10 | 10 100% |
| Utilisation d’une adresse de pile expirée | 1 | — | 0 | 2 | 2 100% |
| Exposition des informations par le biais d’une exception | 1 | — | 0 | 2 | 2 100% |
| Stockage de texte en clair des informations sensibles à l’aide de la classe « Propriétés » | 1 | — | 0 | 1 | 1 100% |
| 서명된 오버플로 검사 | 1 | — | 0 | 3 | 3 100% |
| Injection de fragment Android | 1 | — | 0 | 1 | 1 100% |
| Échec de l’abandon de la session | 1 | — | 0 | 2 | 2 100% |
| Suspicious date format | 1 | — | 0 | 10 | 10 100% |
| Consulta de banco de dados em um loop | 1 | — | 0 | 1 | 1 100% |
| Внедрение удаленных свойств | 1 | — | 0 | 2 | 2 100% |
| Taille d’allocation non contrôlée | 1 | — | 0 | 2 | 2 100% |
| Missing variable declaration | 1 | — | 0 | 9 | 9 100% |
| Appels au code non managé | 1 | — | 0 | 2 | 2 100% |
| Falsche Suffix-Prüfung | 1 | — | 0 | 5 | 5 100% |
| Utilisation d’un algorithme de cryptage défectueux ou risqué | 1 | — | 0 | 3 | 3 100% |
| Unsafe dynamic method access | 1 | — | 0 | 10 | 10 100% |
| CodeQL-supported languages and frameworks | 1 | — | 0 | 1 | 1 100% |
| Texte DOM réinterprété en tant que HTML | 1 | — | 0 | 2 | 2 100% |
| Spurious Javadoc @param tags | 1 | — | 0 | 10 | 10 100% |
Frequently Asked Questions
What anchor texts are used to link to codeql.github.com?
This page shows all anchor texts found in backlinks pointing to codeql.github.com, sorted by the number of referring domains using each anchor. Anchor texts range from branded terms (like the domain name itself) to keyword-rich phrases that describe the linked content. The distribution of anchor texts reveals how other websites perceive and describe codeql.github.com.
What is anchor text?
Anchor text is the visible, clickable text in a hyperlink. Search engines use anchor text as a signal to understand what the linked page is about. For example, if many sites link to a page using the anchor text "best running shoes," search engines infer that the page is relevant to that topic. Anchor text appears in several forms: exact-match (contains target keywords), branded (uses the company or domain name), generic (like "click here"), and naked URLs.
Why is anchor text analysis important for SEO?
Anchor text analysis helps identify potential SEO risks and opportunities. A natural backlink profile has diverse anchor texts including branded terms, generic phrases, and topic-relevant keywords. Over-optimization, where too many backlinks use the same exact-match keyword anchor, can trigger search engine penalties. Conversely, understanding which anchors drive the most authority (measured by referring domain count and DR) helps prioritize link building efforts.
How many unique anchor texts does codeql.github.com have?
The anchor text report for codeql.github.com displays all distinct anchor texts grouped by their hash. Each row shows how many unique referring domains use that anchor, the total number of links, and the dofollow percentage. A high number of unique anchors generally indicates a healthy, natural backlink profile with diverse link sources.