As an aside, if it isn't easy to have an attribute at the global script level, then maybe PSSA could use a comment convention e.g.:

#pragma PSScriptAnalyzer disable PSUseDeclaredVarsMoreThanAssignments
... for the rest of the script, this warning is disabled

and

#pragma PSScriptAnalyzer disable PSUseDeclaredVarsMoreThanAssignments
... for script between these pragmas, the warning is disabled
#pragma PSScriptAnalyzer enable PSUseDeclaredVarsMoreThanAssignments

The problem, I think, is that for this to work it would require a change to PowerShell (maybe v7) to recognize #pragma directives and put them in the AST. This syntax could be generalized for use by any module willing to look for such pragma's in a script's AST e.g.:

#pragma <pragma-name> <pragma-arguments>
# For PowerShell modules, you'd use this format:
#pragma <module-name> <module-specific-directive> <arg>[,<arg>]

See https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma and https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma-warning

Now, these are not "compiler directives" so perhaps pragma isn't the best name but I still think the concept would be easier to work with and more flexible (disabling and re-enabling around sections of the script) than using a SuppressMessage attribute.

Are you putting that attribute on a param() @rkeithhill ?

No. Just at the top of the file. I tried putting it on an empty param () at the beginning of the file but that didn't work either.

Yeah, actually, just tested ... it looks like the suppression only works on named functions.

PSSA is looking for a FunctionAst, therefore if you put a param() at the top of that file (the attribute goes on top), then that does work:

[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseDeclaredVarsMoreThanAssignments', '')]
param()

$unused1 = Get-Foo
$unused2 = Get-Bar

Issue #849 tracks more sophisticated suppression syntax

Oh, and also: #1295

Going to mark this a duplicate and track this issue with #849 and #1295