Writing secure code for Drupal
Registered authoritative source
Canonical secure-development practices for Drupal module/theme/site code.
| Source id | drupal-secure-code |
|---|---|
| Canonical URL | https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/writing-secure-code-for-drupal |
| Trust tier | authoritative |
| Category | secure-development |
| Lifecycle | active |
| Check cadence | 30 day(s) |
| Last successfully observed | 2026-09-08T15:02:49Z (15 day(s) ago) |
| Current source state | within its check cadence |
| Snapshot digest | sha256:f57c9014ebb02fdef09c649f4d56e7645a727d5075034cd13e19d1f92d7c31a8 |
What the freshness state means
Freshness says when this source was last read, and nothing more. A source past its check cadence is one nobody has looked at recently. It is not a source known to be wrong, and the records derived from it are unchanged.