clamxir alternatives and similar packages

Based on the "Security" category.
Alternatively, view clamxir alternatives based on common mentions on social networks and blogs.

site_encrypt

8.6 7.0 clamxir VS site_encrypt

Integrated certification via Let's encrypt for Elixir-powered sites
ssl_verify_fun

7.0 3.2 clamxir VS ssl_verify_fun

Collection of ssl verification functions for Erlang

WorkOS - The modern identity platform for B2B SaaS

The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

Promo workos.com

EmailGuard

4.4 0.0 clamxir VS EmailGuard

Elixir library for detecting disposable (burner) or non-business email addresses.
pwned

3.8 0.0 clamxir VS pwned

Check if your password has been pwned
ca

3.3 8.5 clamxir VS ca

🛡️ CA: Certificate Authority. ДСТУ: 4145. ITU/IETF: 3279, 5755, X.501, X.509, X.511, X.520.
safetybox

3.1 0.0 clamxir VS safetybox

Security oriented helper functions for Elixir
ssl_verify_hostname

2.1 0.0 clamxir VS ssl_verify_hostname

Erlang library for certificate hostname validation based on rfc6125.
code_signing

1.0 0.0 clamxir VS code_signing

Elixir library for signing and verifying BEAM files with Ed25519 signatures
Password

0.6 0.0 clamxir VS Password

Flexible password policies for Elixir.

Do you think we are missing an alternative of clamxir or a related project?

Add another 'Security' Package

Popular Comparisons

README

Clamxir

ClamAV wrapper for elixir based on clamby

This package depends of clamav installed on your system. Please refer to: https://www.clamav.net/documents/installing-clamav.

As recomendation, use the daemonize flag on the configs, in order to improve performance.

Installation

The package can be installed by adding clamxir to your list of dependencies in mix.exs:

def deps do
  [
    {:clamxir, "~> 0.1.8"}
  ]
end

Usage

Clamxir receive the configs on each public method, and based on the configs, will perform their task.

The config file by default is the struct %Clamxir{}. The default values of the structure are:

%Clamxir{
  daemonize: false,
  stream: false,
  check: fase
}

daemonize is a flag to use one instance of the clamav instead of the creation of new instances for each request.

iex> Clamxir.safe?(%Clamxir{}, "/path/file")

stream will pass the argument --stream to clamdscan, this will help to avoid permission issues.

iex> Clamxir.safe?(%Clamxir{stream: true}, "/path/file")

check flag will add validation of the scanner availability before try to run it.

iex> Clamxir.safe?(%Clamxir{check: true}, "/path/file")

Integration with Phoenix

Install as dependency mix.exs

{:clamxir, "~> 0.1.8"}

Use in the controller action where the files are uploaded

def upload(conn, params) do
  file = params["index"]["file"]
  # Requires to have clamavdscann to work
  case Clamxir.safe?(%Clamxir{daemonize: true}, file.path) do
    true ->
      # Process the file and ...
      conn
      |> put_flash(:info,  "Created successfully")
      |> redirect(to: "/")
    false -> conn
      |> put_flash(:error,  "Virus!!")
     |> redirect(to: "/")
  end
end

For a working sample please refer to: https://github.com/ramortegui/sample_phoenix_clamxir

Docs can be found at https://hexdocs.pm/clamxir.