DateParseNormalizationUnchecked

warning native off by default

Group: Probable bugs

Detect createFromFormat on a literal calendar date whose fields require normalization or whose parsing diagnostics are not checked before accepting the parsed value.

Example

<?php
$day=DateTimeImmutable::createFromFormat('!Y-m-d','2025-02-31');

Reported:

• line 2: Reject or explicitly accept normalized calendar dates.

Detection

• Report createFromFormat on a literal calendar date whose fields require normalization or whose parsing diagnostics are not checked before accepting the parsed value.
• Resolve builtin calls and named arguments before checking the contract. Project-local callees are considered only when their bodies or immutable summaries establish the required facts. The default is disabled; enable only when the stated intent matches the application.
• For flow-dependent conditions, require a reachable source-to-use path with no intervening invalidation. Unknown calls, ambiguous aliases or recursion cannot establish definite facts. When the proof is inconclusive, nothing is reported.

Exceptions (no report)

• Explicit diagnostics validation after the parse in the same function scope, through the static getLastErrors() method of DateTime/DateTimeImmutable or the resolved builtin function date_get_last_errors() (its procedural equivalent), intentional overflow, unknown format and input, or invalid parsing already rejected are excluded.
• Unresolved targets, incomplete required facts, suppressed findings and PHP versions lacking the referenced API or language feature produce no report. User declarations shadowing builtin names are not builtin contracts.

Fix

No automatic fix: the application must choose rejection or normalization policy.

PHP versions

Apply only on PHP versions supporting the referenced APIs and syntax (within PHP 5.3–8.5). Builtin behavior and argument contracts follow the configured PHP version. Extension-specific calls require resolved extension API symbols; do not treat same-named application functions as extension calls.

Options

None. Enable or disable this rule through normal rule configuration.

Configure

In custos.json:

{
  "rules": {
    "DateParseNormalizationUnchecked": {
      "enabled": true
    }
  }
}

Suppress

Before the statement or declaration (or the first statement of the file):

// @custos-ignore DateParseNormalizationUnchecked