== Safety concerns

TIP: In general, it is not recommended to execute Eldev, GNU Make,
Scons, any other build tool or anything based on one in a directory
that contains untrusted code.

Like many (if not most) other development tools, Eldev is unsafe when
executed on untrusted code.  For example, simply running `eldev` in a
project you have just downloaded from `hackerden.org` can result in
anything, including emptied home directory.  For that matter, running
`make` or `gradle` is not better in this regard.  Eldev is perhaps _a
bit_ more dangerous, because even `eldev help` reads file `Eldev`,
thus executing arbitrary code.

Even seemingly harmless things, like opening a `.el` file in Emacs can
lead to unforeseen consequences.  If you e.g. have
{uri-flycheck}[Flycheck] or {uri-flymake}[Flymake] enabled everywhere,
this will result in byte-compiling said file, which also can execute
arbitrary code, for example using `(eval-when-compile ...)` form.  The
same holds for installing (not even using!) Elisp packages.

Only use build tools on code that you trust.  Better yet, don’t even
touch code that you don’t plan running.
