Knowledge
Reviewed Drupal Knowledge
11 record(s) in Drupal Knowledge 1.1.3. Every entry below carries the same trust class.
- Drupal 11 API reference is branch-scopedThe Drupal 11 API reference is authoritative for Drupal 11.x API reference material and is generated from comments embedded in Drupal source code.
- Drupal API documentation is version-awareDrupal API guidance must preserve Drupal version context because each Drupal version introduces APIs and keeps only some APIs from previous major versions.
- Drupal core change records preserve introduced branch and versionDrupal core change records are the official record of the release branch and release version in which a change occurred.
- Current Drupal Coding Standards are on GitLab PagesThe Drupal Coding Standards project links to the current GitLab Pages standards, while the historical Drupal.org coding standards guide is marked obsolete and deprecated; the current standards state that they are version-independent and always-current.
- Approved PHP coding standards map to PHPCS, Coder, or PHP_CodeSniffer workThe Drupal Coding Standards process describes how approved PHP standards are handled depending on whether a PHPCS rule exists, needs modification in Coder, or needs new support in Coder or PHP_CodeSniffer.
- Drupal security advisory streams are scopedDrupal core security advisories, contributed-project security advisories, and Security Team public service announcements are distinct source streams with different roles.
- Action routes should use Drupal routing CSRF protectionDrupal secure-code documentation says CSRF protection is integrated into the routing access system and should be used for URLs that perform actions or operations and do not use a form callback.
- Use Drupal database placeholders instead of concatenating SQLDrupal secure-code documentation says data must never be concatenated directly into SQL queries and directs developers to use proper argument substitution, select queries, escapeLike() for LIKE values, and fixed operator choices.
- Twig output escaping should not be bypassed without trusted dataDrupal secure-code documentation says Twig auto-escapes printed strings by default, warns that the raw filter does not escape output and should only be used for trusted data, and states that rendered Twig attributes should be quoted.
- Drupal release metadata can attach the literal "Insecure" Release type term to a core release rowSOURCE FACT: the Drupal update-status release-history feed can attach a Release type taxonomy term whose literal value is "Insecure" to an individual Drupal core release row. PROJECT JOIN: a future finding evaluator may match this only when the Project Analyzer observed installed Drupal core version matches that exact release row in the canonical reviewed release lifecycle context. DRUPAL SEMANTICS (reviewed): For Drupal Update Manager release metadata, a release carrying Release type "Insecure" is treated as insecure; when that exact release is installed, Drupal assigns NOT_SECURE status, whose documented meaning is that the project is missing security update(s). LIMITS: this reviewed meaning does not establish an exploit path, a specific CVE identifier, a finding severity level, or any compromise claim about a project.
- Drupal core release state comes from the official update feedThe official Drupal update-status release-history feed exposes project status, supported branches, release versions, release types, and security coverage, so release-aware knowledge should watch that source instead of hard-coding the latest Drupal version.