Rule Proposal: Warn on dot-sourced function

I've inherited a project where everything is in, for lack of a better description, undeclared global scope, spread across several files. Functions don't have always have parameters, and are called with a dot before the function name. Variables are treated as global, though not declared. For example:

c:\Utils.ps1

function Write-MyLog {
$itemToLog | out-file c:\mylog.txt -append
}

c:\Interface.ps1

. c:\Utils.ps1

$itemToLog = "Something happened"
. Write-MyLog

Miraculously, this all works. Of course, I dare not change anything.

I would love it if ". Write-MyLog" came up as a warning, and even more so if there were some indication that "$itemToLog" in C:\Interface.ps1 was being used by the function called from c:\Utils.ps1.

まず、サンプルスクリプト c:\Utils.ps1 と c:\Interface.ps1 での動作を再現し、dot-sourced 関数呼び出しと、ファイルをまたぐ $itemToLog 変数に注目します。完了とは、アナライザーが要求された構造について警告し、変数の使用状況について要求された情報を提供し、スコープと想定される診断が合意されていることです。