Legacy compatibility for modules (and scripts)

How can I tell (in general) if a script or module I’ve downloaded is compatible with Powershell v2.0?

…And Specifically:

Or do I use the “guess and check” method?

The author did not use the

#Requires -Version 
or it was not available when it was written. As always it is best practice to run any code you would load on a non production system first. If it has powershell v2.0 can test it there. If it has a higher version you can open a session for version 2.0
powershell -version 2.0
and test that way.

Awesome, didn’t know I could just run it like that locally. And yes, I have a lab env.

found more info, for the people.