Anchors
| Anchor text | Ref. domains ▾ | Top DR | Ref. pages | Links to target | Dofollow links |
|---|---|---|---|---|---|
| Cookie de servidor confidencial exposto ao cliente | 1 | — | 0 | 5 | 5 100% |
| Query built from user-controlled sources | 1 | — | 0 | 28 | 28 100% |
| Zéro threads définis pour java.util.concurrent.ScheduledThreadPoolExecutor | 1 | — | 0 | 1 | 1 100% |
| Разрешение внешней сущности XML в управляемых пользователем данных | 1 | — | 0 | 3 | 3 100% |
| Futile conditional | 1 | — | 0 | 7 | 7 100% |
| Divulgação de informações locais em um diretório temporário | 1 | — | 0 | 5 | 5 100% |
| Unvollständiges Zeichenketten-Escaping oder -Codierung | 1 | — | 0 | 10 | 10 100% |
| 사용자 제어 스타일시트를 사용한 XSLT 변환 | 1 | — | 0 | 1 | 1 100% |
| Bloco inacessível except | 1 | — | 0 | 2 | 2 100% |
| Android에서 인증서 고정 누락 | 1 | — | 0 | 1 | 1 100% |
| Verificação de igualdade em valores de ponto flutuante | 1 | — | 0 | 1 | 1 100% |
| 사용자 제어 원본에서 빌드된 SQL 쿼리 | 1 | — | 0 | 3 | 3 100% |
| Dados confidenciais lidos da solicitação GET | 1 | — | 0 | 8 | 8 100% |
| L’appel à la fonction d’accès à la mémoire peut entraîner un dépassement de la mémoire tampon | 1 | — | 0 | 2 | 2 100% |
| 신뢰 경계 위반 | 1 | — | 0 | 1 | 1 100% |
| Assainissement de sous-chaîne d’URL incomplet | 1 | — | 0 | 4 | 4 100% |
| Les instructions 'if' imbriquées peuvent être combinées | 1 | — | 0 | 2 | 2 100% |
| Opportunité « readonly » manquée | 1 | — | 0 | 2 | 2 100% |
| 사용자 제어 입력과 함께 Kernel.open, IO.read 또는 유사 싱크 사용 | 1 | — | 0 | 3 | 3 100% |
| Clientseitige Anforderungsfälschung | 1 | — | 0 | 5 | 5 100% |
| Потенциально переполнение записи | 1 | — | 0 | 4 | 4 100% |
| Injection de langage d’expression (Spring) | 1 | — | 0 | 1 | 1 100% |
| Utilisation d'un algorithme de hachage de chiffrement inapproprié sur les mots de passe | 1 | — | 0 | 4 | 4 100% |
| Information exposure through transmitted data | 1 | — | 0 | 38 | 38 100% |
| Consulta criada a partir de fontes controladas pelo usuário | 1 | — | 0 | 5 | 5 100% |
| Multiple calls to __init__ during object initialization | 1 | — | 0 | 10 | 10 100% |
| Utilisation d’une clé de chiffrement faible | 1 | — | 0 | 3 | 3 100% |
| Identical operands | 1 | — | 0 | 17 | 17 100% |
| Insecure Mass Assignment | 1 | — | 0 | 14 | 14 100% |
| CreateProcess 호출 시 따옴표가 없는 경로가 있는 NULL 응용 프로그램 이름 | 1 | — | 0 | 3 | 3 100% |
| Creating an ASP.NET debug binary may reveal sensitive information | 1 | — | 0 | 38 | 38 100% |
| Log injection | 1 | — | 0 | 56 | 56 100% |
| 元数据要求 | 1 | — | 0 | 2 | 2 100% |
| Nicht übereinstimmende neu/frei oder malloc/delete | 1 | — | 0 | 6 | 6 100% |
| Suspicious unused loop iteration variable | 1 | — | 0 | 10 | 10 100% |
| Uncontrolled allocation size | 1 | — | 0 | 56 | 56 100% |
| Backup de aplicativo permitido | 1 | — | 0 | 5 | 5 100% |
| Use of a broken or weak cryptographic hashing algorithm on sensitive data | 1 | — | 0 | 124 | 124 100% |
| QL プログラムの評価 | 1 | — | 0 | 3 | 3 100% |
| 路径表达式中使用的不受控数据 | 1 | — | 0 | 10 | 10 100% |
| ユーザーが制御するデータの逆シリアル化 | 1 | — | 0 | 1 | 1 100% |
| 安全でない一括割り当て | 1 | — | 0 | 1 | 1 100% |
| Cast non vérifié dans la méthode Equals | 1 | — | 0 | 2 | 2 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.