trend-tracker

To track WordPress security scan findings, you compare current diagnostic results against historical data. This classifies issues as [NEW] or [RECURRING] by maintaining a rolling history of scan data for ongoing trend analysis.

The best way to classify recurring vulnerabilities is to compare current scan data against historical trends stored in memory. This automatically patches inline [RECURRING] or [NEW] badges onto report findings for targeted remediation.

Issue trend analysis works by comparing current diagnostic scan results against a two-slot rolling history of previous data. It patches inline badges onto findings to indicate whether an issue is newly discovered or has persisted across scans.

You do not need a live WordPress connection to track issue trends. The trend analysis operates solely on scan result data without direct WordPress interaction, classifying findings by comparing them against stored historical trends.

Yes, you can use historical scan data to patch inline badges onto security findings. The system compares current diagnostic results against a rolling history and automatically patches [NEW] or [RECURRING] labels directly onto the report.

The limitation of a two-slot rolling history for trend analysis is that it only stores the current and immediately previous scan. This restricts trend visibility to a short window, preventing long-term diagnostic pattern analysis across multiple historical scans.