Saravanan666/pypi-org huggingface dataset:
Package: certbot-dns-ispconfig-ddns
certbot-dns-ispconfig-ddnsISPConfigDNS Authenticator plugin forCertbotusing tokens from the ISPConfigDDNS moduleThis plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records.Configuration of ISPConfigIn theDNS -> Dynamic DNS -> Tokensyou need to have a token with the following rights:Allowed zones: all DNS zones for which you want to create ssl certificatesAllowed record types:TXTLimit records:_acme-challengeIf you want to create certificates for subdomains, they must be included in the Limit records:_acme-challenge,_acme-challenge.subdomain1,_acme-challenge.subdomain2Installationpip install certbot-dns-ispconfig-ddnsUsageCredentials file or cli parametersYou can either use cli parameters to pass authentication information to certbot:...
--dns-ispconfig-ddns-endpoint <your-ispconfig-url (e.g. https://server.example.com:8080>
--dns-ispconfig-ddns-token <your-ddns-token>Or to prevent your credentials from showing up in your bash history, you can also create a
credentials-fileispconfig-ddns.ini(the name does not matter) with the following content:dns_ispconfig_ddns_endpoint=<your-ispconfig-url (e.g. https://server.example.com:8080>dns_ispconfig_ddns_token=<your-ddns-token>And then instead of using the--dns-ispconfig-ddns-*parameters above, you can use...
--dns-ispconfig-ddns-credentials </path/to/your/ispconfig-ddns.ini>You can also mix these usages, though the cli parameters always take precedence over the ini file.ExamplesTo acquire a single certificate for bothexample.comand*.example.com:certbot certonly \
    --non-interactive \
    --agree-tos \
    --email <your-email> \
    --preferred-challenges dns \
    --authenticator dns-ispconfig-ddns \
    --dns-ispconfig-ddns-endpoint <https://server.example.com:8080> \
    --dns-ispconfig-ddns-token <your-ddns-token> \
    --dns-ispconfig-ddns-propagation-seconds 60 \
    -d 'example.com' \
    -d '*.example.com'DockerIn order to create a docker container with a certbot-dns-ispconfig installation,
create an empty directory with the followingDockerfile:FROMcertbot/certbotRUNpipinstallcertbot-dns-ispconfig-ddnsProceed to build the image::docker build -t certbot/dns-ispconfig-ddns .Once that's finished, the application can be run as follows::docker run --rm \
    -v /var/lib/letsencrypt:/var/lib/letsencrypt \
    -v /etc/letsencrypt:/etc/letsencrypt \
    --cap-drop=all \
    certbot/dns-ispconfig-ddns certonly \
    --non-interactive \
    --agree-tos \
    --authenticator dns-ispconfig-ddns \
    --dns-ispconfig-ddns-propagation-seconds 60 \
    --dns-ispconfig-ddns-credentials /etc/letsencrypt/.secrets/domain.tld.ini \
    -d example.com -d '*.example.com'
Package: certbot-dns-isset
Isset Certbot pluginThe Certbot Authenticator for the Isset Customer DNS API.Installationpip3installcertbot-dns-issetHow to useEnsureisset.inicontains:certbot_dns_isset:dns_isset_endpoint="https://customer.isset.net/api"certbot_dns_isset:dns_isset_token="<token>"Fix credentials permissions:chmod600isset.iniDry-runcertbotcertonly--dry-run\-acertbot-dns-isset:dns-isset--certbot-dns-isset:dns-isset-credentialsisset.ini\-memail@yourdomain.tld--agree-tos\-dyourdomain.tldProduction (non-interactive)certbotcertonly-n\-acertbot-dns-isset:dns-isset--certbot-dns-isset:dns-isset-credentialsisset.ini\-memail@yourdomain.tld--agree-tos\-dyourdomain.tld
Package: certbot-dns-leaseweb
certbot-dns-leasewebA certbot plugin that automates the process of completing a dns-01 challenge
using Leaseweb'sDomain API.Installcertbot-dns-leasewebshould be installed via pip, in the same python
environment in whichcertbotis installed:pip install certbot-dns-leasewebUsageUse the following flags tocertbotto use and control this plugin:OptionDescription--authenticator dns-leasewebrequired, enable and use this plugin.--dns-leaseweb-credentialsrequired, Leaseweb API credentials INI file.--dns-leaseweb-propagation-secondsoptional, seconds to wait for DNS records to propagate.CredentialsA suitable API token can be generated fromhttps://secure.leaseweb.com/api-client-management/.The token should then be stored in an INI file:dns_leaseweb_api_token = notarealtokenCAUTION: These API credentials should be carefully protected from exposure
and unauthorised access.They could be used to complete DNS challenges, allowing potentially unauthorised
parties to obtain or revoke certificates for your domains.ExamplesObtain a wildcard certificate forexample.com:certbot certonly \
  --authenticator dns-leaseweb \
  --dns-leaseweb-credentials leaseweb.ini \
  -d '*.example.com'Obtain a wildcard certificate forexample.com, with extra time for propagation:certbot certonly \
  --authenticator dns-leaseweb \
  --dns-leaseweb-credentials leaseweb.ini \
  --dns-leaseweb-propagation-seconds 600 \
  -d '*.example.com'DockerIf you prefer to run certbot with thedns-leasewebplugin in docker, you can
build a suitable image withmake image.The image comes with a partially-completed CLI as its entrypoint:/usr/local/bin/certbot \
  --authenticator=dns-leaseweb \
  --dns-leaseweb-credentials=/etc/letsencrypt/credentials/leaseweb.iniYou will need to create a suitable credentials file for the plugin at/etc/letsencrypt/credentials/leaseweb.inifor the instructions below to work.You can then use it as:docker run --rm -ti \
  --volume "/etc/letsencrypt:/etc/letsencrypt" \
  --volume "/var/lib/letsencrypt:/var/lib/letsencrypt" \
  certbot-dns-leaseweb:latest \
    certonly \
      --dns-leaseweb-propagation-seconds 600 \
      -d '*.example.com'Issues and developmentPlease report any issues (or improvement suggestions) athttps://gitlab.com/iwaseatenbyagrue/certbot-dns-leaseweb/-/issues.If you want to hack on this project, please make sure you run tests and linting
on your code:make testThanksToLetsencrypt, and the EFF forcertbot.This plugin is adapted fromhttps://github.com/ctrlaltcoop/certbot-dns-hetzner,
whose README was also the template for this file.https://github.com/m42e/certbot-dns-ispconfigwas also consulted during
development of this plugin.
Package: certbot-dns-lightsail
Amazon Lightsail DNS Authenticator Plugin for CertbotThis plugin proves you have control over a domain by DNS-01 challenge to the Amazon Lightsail DNS.Additional Arguments for Certbot--authenticator dns-lightsailUse this plugin as an authenticator. (required)--dns-lightsail-propagation-seconds ${value}The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60, The default TTL for Amazon Lightsail DNS records is 60 seconds so I recommend to set a value greater than it)Getting StartedInstallationInstall this plugin usingpip:pip install certbot-dns-lightsailUsageThis plugin requires AWS region and credential settings before it can be used. And the region must beus-east-1.1. Create Access KeyCreate an access key using IAM policy below:{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":["lightsail:CreateDomainEntry","lightsail:DeleteDomainEntry"],"Resource":"arn:aws:lightsail:us-east-1:${YOUR-ACCOUNT-ID}:Domain/${YOUR-DOMAIN-ID}"}]}2. Create Setting FilesCreate setting files below:# ~/.aws/config
[default]
region=us-east-1

# ~/.aws/credentials
[default]
aws_access_key_id=${YOUR-ACCESS-KEY-ID}
aws_secret_access_key=${YOUR-SECRET-ACCESS-KEY}3. Run CertbotYou are ready to run this plugin with Certbot!For example, run command below to obtain a certificate using this plugin:certbotcertonly\--authenticatordns-lightsail\--dns-lightsail-propagation-seconds70\--non-interactive\--agree-tos\-m'mail@example.com'\-d'example.com'\-d'*.example.com'
Package: certbot-dns-local
certbot-dns-localDomain registrar agnostic authenticator plugin for certbotAn authenticator plugin forcertbotto supportLet's EncryptDNS
challenges (dns-01) for domains managed by any registrar.Why use this authenticator plugin?There is no other authenticator plugin for your domain registrar.Some domain registrars do not support fine-grained API permissions. Storing domain registrar credentials in a file on
a web server might pose a security risk to all your domains.Migrating from one domain registrar to another does not require a new authenticator plugin.InstallationOptionally install thenetfilter_queuelibrary. On Debian-based systems, run:apt install libnetfilter-queue-devThe library enables support for DNS challenge authentication if UDP port 53 is already occupied.Plugin installation:If you are usingcertbotfrom your distribution repository or from the Python Package Index:pip install certbot-dns-localIf you are usingcertbot-auto, clone the repository,cdinto the folder and run:/opt/eff.org/certbot/venv/bin/pip install certbot-dns-localSet up a DNSNSrecord for_acme-challenge.yourdomain.compointing to the server which certbot is running on.For example:_acme-challenge.yourdomain.com. 300 IN NS yourdomain.com.Such a record has to be created for each subdomain which you want to obtain a certificate for.UsageA new certificate can be requested as follows:certbot certonly -a certbot-dns-local:dns-local -d yourdomain.com -d '*.yourdomain.com'Renewals will automatically be performed using the same authenticator by certbot.Behind the curtainBehind the curtain, the plugin will open a UDP server on port 53 in order to serve the DNS validations. In case binding
to port 53 fails because it is already occupied by another application, it will fall back to packet interception using thenetfilter_queuelibrary.
Package: certbot-dns-loopia
Loopia DNS Authenticator for CertbotThis allows automatic completion ofCertbot’sDNS01 challange for domains managed onLoopiaDNS.Installing$ sudo pip install certbot-dns-loopiaNote that you should normally install this asroot, unless you know what
you are doing.UsageThe plugin requires the following permissions enabled for your Loopia API user:addZoneRecordgetZoneRecordsremoveSubdomainremoveZoneRecordTo use the authenticator you need to provide some required options:--dns-loopia-credentials(required)INI file withuserandpasswordfor your Loopia API user.usernormally has the formatuser@loopiaapi.The credentials file must have the folling format:dns_loopia_user = user@loopiaapi
dns_loopia_password = passwordgoeshereFor safety reasons the file must not be world readable. You can solve this by
running:$ chmod 600 credentials.iniThen you can runcertbotusing:$ sudo certbot certonly \
    --authenticator dns-loopia \
    --dns-loopia-credentials credentials.ini \
    -d domain.comIf you want to obtain a wildcard certificate you can use the domain-d*.domain.com.Known issuesDue to caching on Loopia’s side it can take up to 15 minutes before changes
propagates. Therefore the plugin will wait 15 minutes before contacting the
ACME server.
It has been known to work with as little as 90 seconds and sometimes less
and if you want to try something other than 15 minutes then add--dns-loopia-propagation-seconds90to parameters for 90 seconds or
how many seconds you want.ChangelogVersion 1.0.0Released 4th May 2021This is a breaking change. The CLI arguments and the name of the package has
changed to match other DNS authenticator plugins.Thank you Peter Magnusson (@kmpm) for contributing
this change!Updated name tocertbot-dns-loopiato match other DNS pluginsDropped Python < 3.6 supportVersion 0.2.0Released 21st August 2017Rewrote plugin to match the implementation ofcertbot-dns-*pluginsUpdated dependency requirements since the old release was completely broken
for neweracmeandcertbot(seeissue #2)Version 0.1.0Released 10th May 2017Initial releaseDisclaimerThis plugin is neither affiliated with nor endorsed by Loopia AB.
Package: certbot-dns-myonlineportal
certbot-dns-myonlineportalMyOnlinePortal DNS Authenticator plugin forCertbot.This plugin is built from the ground up and follows the development style and life-cycle
of othercertbot-dns-*plugins found in theOfficial Certbot Repository.Installationpip install --upgrade certbot
pip install certbot-dns-myonlineportalVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-myonlineportal
Description: Obtain certificates using a DNS TXT record (if you are using
MyOnlinePortal for DNS).
Interfaces: Authenticator, Plugin
Entry point: dns-myonlineportal =
certbot_dns_myonlineportal.dns_myonlineportal:Authenticator

...
...ConfigurationThe credentials file e.g.~/myonlineportal-credentials.inishould look like this:certbot_dns_myonlineportal:dns_myonlineportal_username = username
certbot_dns_myonlineportal:dns_myonlineportal_password = password
certbot_dns_myonlineportal:dns_myonlineportal_endpoint = https://myonlineportal.net/set-acmeUsagecertbot ... \
        --authenticator certbot-dns-myonlineportal:dns-myonlineportal \
        --certbot-dns-myonlineportal:dns-myonlineportal-propagation-seconds 90 \
        --certbot-dns-myonlineportal:dns-myonlineportal-credentials ~/myonlineportal-credentials.ini \
        certonlyDevelopmentBuild the docker containerdocker build -t certbot/dns-myonlineportal .Run the docker containermkdir -p ./var/lib/letsencrypt
mkdir -p ./var/log/letsencrypt
mkdir -p ./etc/letsencrypt
PWD=$(pwd)

docker run \
  --rm \
  -v ${PWD}/var/lib/letsencrypt:/var/lib/letsencrypt \
  -v ${PWD}/var/log/letsencrypt:/var/log/letsencrypt \
  -v ${PWD}/etc/letsencrypt:/etc/letsencrypt \
  --cap-drop=all \
  certbot/dns-myonlineportal certonly --debug \
   --authenticator certbot-dns-myonlineportal:dns-myonlineportal \
   --certbot-dns-myonlineportal:dns-myonlineportal-propagation-seconds 90 \
   --certbot-dns-myonlineportal:dns-myonlineportal-credentials ~/myonlineportal-credentials.ini \
   --no-self-upgrade \
   --agree-tos \
   --email 'my.email@example.com' \
   --keep-until-expiring --non-interactive --expand \
   --server https://acme-v02.api.letsencrypt.org/directory \
   -d example.myonlineportal.net -d '*.example.myonlineportal.net'Run the testspython3 setup.py testBuild the packagepython3 -m buildUpload to pypipython3 -m twine upload --repository testpypi dist/*Helpful linksMyOnlinePortal api
Package: certbot-dns-navercloud
certbot-dns-navercloudNaverCloud DNS Authenticator plugin for CertbotCreate credentials ini file$nano~/certbot-creds.iniSet access key and secret keydns_navercloud_access_key=<access_key>dns_navercloud_secret_key=<secret_key>Set appropriate permissions$chmod600~/certbot-creds.iniRetrieve the certificate$certbotcertonly\--authenticator'dns-navercloud'\--dns-navercloud-credentials'~/certbot-creds.ini'\-d'*.example.com'
Package: certbot-dns-nextlayer
certbot-dns-nextlayernext layer DNS Authenticator plugin forCertbot.This plugin is built from the ground up and follows the development style and life-cycle
of othercertbot-dns-*plugins found in theOfficial Certbot Repository.Installationpip install --upgrade certbot # optional
pip install certbot-dns-nextlayerVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-nextlayer
Description: Obtain certificates using a DNS TXT record by using the nextlayer
dns api.
Interfaces: IAuthenticator, IPlugin
Entry point: dns-nextlayer = certbot_dns_nextlayer.dns_nextlayer:Authenticator

...
...ConfigurationThe credentials file e.g.~/nldns-credentials.inishould look like this:dns_nextlayer_token=put_your_token_hereUsageExample commandcertbot certonly --authenticator dns-nextlayer --dns-nextlayer-credentials=~/nldns-credentials.ini -d nextlayer.atZone detection methodWe've added the configuration parameter--dns-nextlayer-methodto select the way our certbot plugin determines the correct zone to add the record to. Currently there are 3 options you can choose from.intelligentThis is the default method.It tries to determine the zone intelligently by extracting the TLD and re-adding the first level.Examples:* dns.nextlayer.at: nextlayer.at
* dns.nextlayer.co.at: nextlayer.co.at
* www.dns.nextlayer.co.at: nextlayer.co.atremove-firstThis method just removes the first level of the requested domain.Examples:* dns.nextlayer.at: nextlayer.at
* dns.nextlayer.co.at: nextlayer.co.at
* www.dns.nextlayer.co.at: dns.nextlayer.co.atnoneThis method does what it's called. No magic.Examples:* dns.nextlayer.at: dns.nextlayer.at
* dns.nextlayer.co.at: dns.nextlayer.co.at
* www.dns.nextlayer.co.at: www.dns.nextlayer.co.at
Package: certbot-dns-ngenix
NGENIXDNS Authenticator plugin for CertbotThis plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using the NGENIX Remote API.Named ArgumentsTo start using DNS authentication for NGENIX, pass the following arguments on
certbot’s command line:--authenticatordns-ngenixselect the authenticator plugin (Required)--dns-ngenix-credentialsNGENIX Remote User credentials
INI file. (Required)--dns-ngenix-propagation-secondswaiting time for DNS to propagate before askingthe ACME server to verify the DNS record.(Default: 300, Recommended: >= 600)CredentialsAn examplecredentials.inifile:# NGENIX API credentials used by Certbotdns_ngenix_email=user@domain.tlddns_ngenix_api_token=ngenix_tokenThe path to this file can be provided interactively or using the--dns-ngenix-credentialscommand-line argument. Certbot records the path
to this file for use during renewal, but does not store the file’s contents.Caution!You should protect these API credentials as you would a password. Users who
can read this file can use these credentials to issue arbitrary API calls on
your behalf. Users who can cause Certbot to run using these credentials can
complete adns-01challenge to acquire new certificates or revoke
existing certificates for associated domains, even if those domains aren’t
being managed by this server.Certbot will emit a warning if it detects that the credentials file can be
accessed by other users on your system. The warning reads “Unsafe permissions
on credentials configuration file”, followed by the path to the credentials
file. This warning will be emitted each time Certbot uses the credentials file,
including for renewal, and cannot be silenced except by addressing the issue
(e.g., by using a command likechmod 600to restrict access to the file).Examplescertbotcertonly\\--dns-ngenix\\--dns-ngenix-credentials~/.secrets/certbot/ngenix.ini\\-dexample.comcertbotcertonly\\--dns-ngenix\\--dns-ngenix-credentials~/.secrets/certbot/ngenix.ini\\-dexample.com\\-dwww.example.comcertbotcertonly\\--dns-ngenix\\--dns-ngenix-credentials~/.secrets/certbot/ngenix.ini\\--dns-ngenix-propagation-seconds240\\-dexample.com
Package: certbot-dns-njalla
Certbot plugin for authentication using NjallaThis is a plugin forCertbotthat uses theNjallaAPI
to allow customers to prove control of a domain name.UsageObtain an Njalla API token (found in thesettings)Install the plugin usingpip3 install certbot-dns-njalla, or if you are usingsudowith certbot usesudo -H pip3 install certbot-dns-njallaCreate anjalla.iniconfig file with the following contents and applychmod 600 njalla.inion it:certbot_dns_njalla:dns_njalla_token=0000000000000000000000000000000000000000Replace the zeroes with your Njalla API key and ensure permissions are set
to disallow access to other users.Runcertbotand direct it to use the plugin for authentication and to use
the config file previously created:certbot certonly -a certbot-dns-njalla:dns-njalla --certbot-dns-njalla:dns-njalla-credentials njalla.ini -d domain.comAdd additional options as required to specify an installation plugin etc.DistributionPyPI:https://pypi.org/project/certbot-dns-njalla/
Package: certbot-dns-nodeup
Certbot plugin for authentication using Nodeup APIThis is a plugin forCertbotthat uses the Nodeup API to allowNodeupcustomers to prove control of a domain name.UsageObtain a NodeUp API token (seeNodeup API Settings)Install the plugin usingpip install certbot-dns-nodeupCreate anodeup.iniconfig file with the following contents and applychmod 600 nodeup.inion it:# Nodeup API credentials used by Certbot
dns_nodeup_api_token = TOKENReplaceTOKENwith your Nodeup API token and ensure permissions are set
to disallow access to other users.Runcertbotand direct it to use the plugin for authentication and to use
the config file previously created:certbot certonly -a dns-nodeup --dns-nodeup-credentials nodeup.ini -d example.comWildcardcertbot certonly -a dns-nodeup --dns-nodeup-credentials nodeup.ini -d \*.example.com
Package: certbot-dns-oci
Oracle Cloud Infrastructure DNS Authenticator plugin for CertbotPlugin automates the process of dns-01 challenge by managing TXT records in
the Oracle Cloud Infrastructure DNS service.Installationpip3installcertbot-dns-ociArgumentsNameDescriptionDefault--authenticator dns-ociSelect the pluginRequired--dns-oci-credentialsOCI credentials config file location~/.oci/config--dns-oci-profileProfile name in OCI credentials config fileDEFAULT--dns-oci-propagation-secondsDNS record propagation timeout60Credentials--dns-oci-credentialshas special valueinstance_principalthat switches
certbot to use the instance principal for OCI authentication
(please, read the documentation about the feature.)
Corresponding dynamic group must be able to readdns-zonesin compartment
and managedns-records.In other cases, plugin requires theOCI credentials configuration file,
which is~/.oci/configby default.
The profile can be specified by--dns-oci-profile(usuallyDEFAULT).Examplecertbotcertonly--emailuser@example.com\--authenticatordns-oci-dwww.example.com--dry-runRequirementsoci
certbot
Package: certbot-dns-onecloud
Use the certbot client to generate a certificate using onecloud.Prepare an API TokenFetch an api token by instruction onhttps://1cloud.ru/api/auth/authInstall certbot and pluginpipinstallcertbot-dns-onecloudCreate a credentials filecertbot_dns_onecloud:dns_onecloud_api_token = "ONECLOUD-API-TOKEN"Generate a certificatecertbotcertonly-acertbot-dns-onecloud:dns-onecloud\[--certbot-dns-onecloud:dns-onecloud-credentialsPATH-TO-CREDENTIAL-FILE]-dREPLACE-WITH-YOUR-DOMAIN
Package: certbot-dns-openstack
OpenStack DNS Authenticator plugin for CertbotPlease fill here a long description which must be at least 3 lines wrapped on
80 cols, so that distribution package maintainers can use it in their packages.
Note that this is a hard requirement.Free software: Apache licenseDocumentation:https://docs.openstack.org/certbot-dns-openstack/latestSource:https://git.openstack.org/cgit/openstack/certbot-dns-openstackBugs:https://bugs.launchpad.net/certbot-dns-openstackFeaturesTODO
Package: certbot-dns-ownadmin
certbot-dns-ownadminOwnAdmin Authenticator plugin forCertbot.This plugin is built from the ground up and follows the development style and life-cycle
of othercertbot-dns-*plugins found in theOfficial Certbot Repository.Installationpip install --upgrade certbot
pip install certbot-dns-ownadminVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-ownadmin
Description: Obtain certificates using a DNS TXT record (if you are using
OwnAdmin for DNS.)
Interfaces: Authenticator, Plugin
Entry point: dns-ownadmin = certbot_dns_ownadmin.dns_ownadmin:Authenticator

...ConfigurationThe credentials file e.g.~/ownadmin-credentials.inishould look like this:dns_ownadmin_api_url = https://api.mypowerdns.example.org
dns_ownadmin_api_key = AbCbASsd!@34Usagecertbot ... \
        --authenticator dns-ownadmin  \
        --dns-ownadmin-credentials ~/ownadmin-credentials.ini \
        certonly
Package: certbot-dns-pdns
Certbot DNS Authenticator for PowerDNSPowerDNS DNS Authenticator plugin forCertbot.
This plugin uses the PowerDNS HTTP API to request modifications for the DNS-01 challenge.UsageCreate a credentials file to use with this plugin:~/pdns-credentials.inidns_pdns_endpoint=https://pdns-api.example.comdns_pdns_api_key=<Your API Key>dns_pdns_server_id=localhost# see https://doc.powerdns.com/authoritative/http-api/server.htmldns_pdns_disable_notify=false# Disable notification of secondaries after record changesThe available configuration options correspond to theDNS-Lexicon settings for the PowerDNS provider.Run Certbot using the plugin as the authenticator:certbotcertonly\--authenticatordns-pdns\--dns-pdns-credentials~/pdns-credentials.ini\...LicenseApache License 2.0MaintainerFelix Kaechelefelix@kaechele.ca