Re:GitHub Super Linter: one linter to rule them all
by jwilk on Thursday June 18, 2020 @02:16PM
(#23565926)
Also note that "perl -c" can't be used securely against untrusted code:
$ echo 'BEGIN{`cowsay pwned > /dev/tty`}' > test.pm
$ perl -Mstrict -cw test.pm
_______
< pwned >
-------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
test.pm syntax OK
Re:GitHub Super Linter: one linter to rule them all
by obrajesse on Thursday June 18, 2020 @08:45PM
(#23569822)
Also, it looks like the perl linter only triggers against .pl files and not .pm files
Re:GitHub Super Linter: one linter to rule them all
by zkoppert on Thursday June 18, 2020 @12:15PM
(#23564529)
Yes please! Feel free to open up an issue and collaborate with others to get it added! https://github.com/github/super-linter/issues
The Perl validation seems to be restricted to "compile with warnings", despite "perlcritic" being now almost 15 years old, predating both some other linters' and even some other languages' very existence.
I'll try to see how feasible it'd be to add it as a ("the"?) Perl linter to be used as using just the compilation step to infer everything's fine doesn't really satisfy the role a linter is meant to have.