cpan-security-advisory VS Crypt-LE

Compare cpan-security-advisory vs Crypt-LE and see what are their differences.


Crypt::LE - Let's Encrypt / Buypass / ZeroSSL and other ACME-servers client and library in Perl for obtaining free SSL certificates (inc. generating RSA/ECC keys and CSRs). HTTP/DNS verification is supported out of the box, EAB (External Account Binding) supported, easily extended with plugins, easily dockerized. (by do-know)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
cpan-security-advisory Crypt-LE
1 1
20 348
- -
8.1 2.7
9 days ago about 1 year ago
Perl Perl
Artistic License 2.0 Artistic License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of cpan-security-advisory. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-10.
  • Revitalizing CPAN::Audit
    2 projects | /r/perl | 10 Jun 2022
    In 2018, Viacheslav Tykhanovskyi (VTI) created CPAN::Audit, a program to compare your installed Perl modules against a list of security notices. A couple months ago, a friend asked me about the module and I thought it sounded interesting. I volunteered to update it, so Renée Bäcker and I did just that. Even the most green Perl developer can help too.


Posts with mentions or reviews of Crypt-LE. We have used some of these posts to build our list of alternatives and similar projects.
  • Help me understand Wildcard Certs
    1 project | /r/sysadmin | 11 Apr 2023
    Normally you can use the same .csr forever if the domain is the same - I normally use LE64 to generate let's encrypt certificates (which can do wildcards also), but if you're purchasing a certificate rather than generating a free one, and you want to generate it right in IIS, you can follow a guide like this. If you generate a wildcard cert like *, you can use it for all your subdomains but NOT generally for itself (depending on your application). You can use the same certificate for all applications provided they support whatever format the certificate is in; mostly these will be in PEM-style anymore so you have the whole cert chain in one file.

What are some alternatives?

When comparing cpan-security-advisory and Crypt-LE you can also consider the following projects:

cpan-audit - Check CPAN modules for known security vulnerabilities

caddy-cloudflare - Caddy with integrated support for Cloudflare DNS-01 ACME verification challenges.

clamtk - An easy to use, light-weight, on-demand virus scanner for Linux systems

Netdot - Network Documentation Tool

Data-UUID - perl library for generating universally unique identifiers

mod_md - Let's Encrypt (ACME) in Apache httpd

SpamAssassin - Read-only mirror of Apache SpamAssassin. Submit patches to Do not send pull requests

sslmgr - A layer of abstraction the around acme/autocert certificate manager (Golang)

ImapSync - Imapsync is an IMAP transfers tool. The purpose of imapsync is to migrate IMAP accounts or to backup IMAP accounts. IMAP is one of the three current standard protocols to access mailboxes, the two others are POP3 and HTTP with webmails, webmails are often tied to an IMAP server. Upstream website is

lego - Let's Encrypt/ACME client and library written in Go

acme-companion - Automated ACME SSL certificate generation for nginx-proxy

HandyAcme - A TypeScript Client implements ACME (RFC 8555)