PregMatchFailureAsNonMatch
warning native off by defaultGroup: Probable bugs
Detect preg_match or preg_match_all tested with boolean negation or a falsy branch that handles input rejection without distinguishing false from zero.
Example
php
<?php
if (!preg_match($pattern, $text)) { return false; }Reported:
- line 2: Distinguish regex failure from a successful non-match.
Detection
- Report preg_match or preg_match_all tested with boolean negation or a falsy branch that handles input rejection without distinguishing false from zero.
- 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, recursion or analysis-budget exhaustion cannot establish definite facts.
Exceptions (no report)
- Strict false/zero checks, deliberate combined handling, and unknown wrappers 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: error-handling behavior cannot be invented.
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:
json
{
"rules": {
"PregMatchFailureAsNonMatch": {
"enabled": true
}
}
}Suppress
Before the statement or declaration (or the first statement of the file):
php
// @custos-ignore PregMatchFailureAsNonMatch