===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
elixir-lang-1.10.3.dfsg/lib/elixir/lib/port.ex-91- `:spawn` will retrieve the program name from the argument and traverse your
elixir-lang-1.10.3.dfsg/lib/elixir/lib/port.ex:92: operating system `$PATH` environment variable looking for a matching program.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/port.ex-93-
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/port.ex-100- Spawn executable is a more restricted and explicit version of spawn. It expects
elixir-lang-1.10.3.dfsg/lib/elixir/lib/port.ex:101: full file paths to the executable you want to execute. If they are in your `$PATH`,
elixir-lang-1.10.3.dfsg/lib/elixir/lib/port.ex-102- they can be retrieved by calling `System.find_executable/1`:
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-596- value stored in the registry. The atom `:_` can be used to ignore a given
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:597: value or tuple element, while the atom `:"$1"` can be used to temporarily assign part
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-598- of pattern to a variable for a subsequent comparison.
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-601- Each guard is a tuple, which describes checks that should be passed by assigned part of pattern.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:602: For example the `$1 > 1` guard condition would be expressed as the `{:>, :"$1", 1}` tuple.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-603- Please note that guard conditions will work only for assigned
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:604: variables like `:"$1"`, `:"$2"`, and so forth.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:605: Avoid usage of special match variables `:"$_"` and `:"$$"`, because it might not work as expected.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-606-
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1090- value stored in the registry. The atom `:_` can be used to ignore a given
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1091: value or tuple element, while the atom `:"$1"` can be used to temporarily assign part
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1092- of pattern to a variable for a subsequent comparison.
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1095- Each guard is a tuple, which describes checks that should be passed by assigned part of pattern.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1096: For example the `$1 > 1` guard condition would be expressed as the `{:>, :"$1", 1}` tuple.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1097- Please note that guard conditions will work only for assigned
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1098: variables like `:"$1"`, `:"$2"`, and so forth.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1099: Avoid usage of special match variables `:"$_"` and `:"$$"`, because it might not work as expected.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1100-
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1157- the data stored in the registry, which is `{key, pid, value}`. The atom `:_` can be used to
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1158: ignore a given value or tuple element, while the atom `:"$1"` can be used to temporarily
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1159- assign part of pattern to a variable for a subsequent comparison. This can be combined
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1160: like `{:"$1", :_, :_}`.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1161-
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1163- Each guard is a tuple, which describes checks that should be passed by assigned part of pattern.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1164: For example the `$1 > 1` guard condition would be expressed as the `{:>, :"$1", 1}` tuple.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1165- Please note that guard conditions will work only for assigned
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1166: variables like `:"$1"`, `:"$2"`, and so forth.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1167-
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1168- The third part, the body, is a list of shapes of the returned entries. Like guards, you have access to
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1169: assigned variables like `:"$1"`, which you can combine with hardcoded values to freely shape entries
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1170- Note that tuples have to be wrapped in an additional tuple. To get a result format like
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1171- `%{key: key, pid: pid, value: value}`, assuming you bound those variables in order in the match part,
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1172: you would provide a body like `[%{key: :"$1", pid: :"$2", value: :"$3"}]`. Like guards, you can use
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1173- some operations like `:element` to modify the output format.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1174-
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex:1175: Do not use special match variables `:"$_"` and `:"$$"`, because they might not work as expected.
elixir-lang-1.10.3.dfsg/lib/elixir/lib/registry.ex-1176-
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex-178- Whenever you start a new process, Elixir annotates the parent of that process
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex:179: through the `$ancestors` key in the process dictionary. This is often used to
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex-180- track the hierarchy inside a supervision tree.
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex-188-
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex:189: To track the relationship between your code and the task, we use the `$callers`
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex-190- key in the process dictionary. Therefore, assuming the `Task.Supervisor` call
##############################################
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex-201- The list of callers of the current process can be retrieved from the Process
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex:202: dictionary with `Process.get(:"$callers")`. This will return either `nil` or
elixir-lang-1.10.3.dfsg/lib/elixir/lib/task.ex-203- a list `[pid_n, ..., pid2, pid1]` with at least one entry Where `pid_n` is
##############################################
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger.ex-275- * `:format` - the format message used to print logs.
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger.ex:276: Defaults to: `"\n$time $metadata[$level] $levelpad$message\n"`.
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger.ex-277- It may also be a `{module, function}` tuple that is invoked
##############################################
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger.ex-280-
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger.ex:281: * `:metadata` - the metadata to be printed by `$metadata`.
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger.ex-282- Defaults to an empty list (no metadata).
##############################################
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex-17-
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:18: * `$time` - the time the log message was sent
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:19: * `$date` - the date the log message was sent
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:20: * `$message` - the log message
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:21: * `$level` - the log level
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:22: * `$node` - the node that prints the message
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:23: * `$metadata` - user controlled data presented in `"key=val key2=val2 "` format
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:24: * `$levelpad` - sets to a single space if level is 4 characters long,
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex-25- otherwise set to the empty space. Used to align the message after level.
##############################################
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex-38- to the current process. The user can configure the backend to choose
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex:39: which metadata it wants to print and it will replace the `$metadata`
elixir-lang-1.10.3.dfsg/lib/logger/lib/logger/formatter.ex-40- value.
##############################################
elixir-lang-1.10.3.dfsg/lib/mix/lib/mix/tasks/format.ex-81-
elixir-lang-1.10.3.dfsg/lib/mix/lib/mix/tasks/format.ex:82: where `$file` refers to the current file and `$project` is the root of your
elixir-lang-1.10.3.dfsg/lib/mix/lib/mix/tasks/format.ex-83- project.
##############################################
elixir-lang-1.10.3.dfsg/lib/mix/lib/mix/tasks/release.ex-737- files to. It can be set to a custom directory. It defaults to
elixir-lang-1.10.3.dfsg/lib/mix/lib/mix/tasks/release.ex:738: `$RELEASE_ROOT/tmp`
elixir-lang-1.10.3.dfsg/lib/mix/lib/mix/tasks/release.ex-739-