A recent thread (Best option for "switch/case" functionality?) might provide you with some documentation links and alternatives.

Personally, I've used Switch::Plain without issues, but it's limited functionality ("simple string or numeric equality tests") might not meet everyone's needs.

I'm not seeing anything on cpan saying it's depreciated.

That's because it's not depreciated deprecated.

perlcritic's claim that Switch was deprecated is incorrect. It was simply removed from the perl distribution. That said, it's its removal from the distribution that perlcritic is warning you about. The solution, however, isn't to switch to another module; it's simply to mark Switch as a dependency of your distributable so it gets installed by cpan (or cpanm or whatever).

That said, many dislike Switch because it can issue misleading error messages because it's based on a source filter. You might want to look for an alternative anyway. (An if statement with a bunch of elsif clauses usually works just fine.)

for my $age (qw/ 1 7 14 21 75/) {
    my $person = $age <  2 ? "baby" 
               : $age < 13 ? "kid" 
               : $age < 18 ? "teen"
               : $age < 65 ? "adult"
               : "senior";
    print "$age : \t $person \n";
}
[download]

Does your code(-base) use Switch;? If so, see Switch. It prominently states in the section NAME

Switch - A switch statement for Perl, do not use if you can use given/when

Also, see the BUGS section:

There are undoubtedly serious bugs lurking somewhere in code this funky :-) Bug reports and other feedback are most welcome.
May create syntax errors in other parts of code.
On perl 5.10.x may cause syntax error if "case" is present inside heredoc.
In general, use given/when instead. It were introduced in perl 5.10.0. Perl 5.10.0 was released in 2007.

So the perl you are using has given/when, and you'd better scan your codebase, remove any use Switch and replace switch/case with given/when instead of silencing Perl::Critic.

As are most things, Perl::Critic is configurable. All you have to do is set the policy.

One of the things you'll find is that the default policy is probably no longer the best one. On IRC, the many questions and answers have allowed people there to build up their own policy in Perl::Critic::Freenode. I'd suggest you look into that.

On Switch, though, it's frowned upon by most because it uses source filters instead of pluggable keywords. You can see the reasons in the description of Switch::Plain that was mentioned above.