DSA candidates
assigned
--
enigmail
--
flightcrew
--
glib2.0
--
golang-go.crypto
--
imagemagick
--
jackd2
--
libapache2-mod-auth-mellon
--
libgcrypt20
--
libxslt
--
mupdf
--
openjpeg2
--
python-urllib3
--
ruby-openid
--
unzip
--
calamares/stable
--
libsass/stable
--
php7.3/stable
--
python3.7/stable
--
ruby-omniauth/stable
--
squid/stable
--
tomcat9/stable
--
ceph/oldstable
--
firejail/oldstable
--
gnutls28/oldstable
--
golang-github-seccomp-libseccomp-golang/oldstable
--
gvfs/oldstable
--
jackson-databind/oldstable
--
jasperreports/oldstable
--
jupyter-notebook/oldstable
--
kf5-messagelib/oldstable
--
libspring-java/oldstable
--
monit/oldstable
--
openvswitch/oldstable
--
otrs2/oldstable
--
pacemaker/oldstable
--
php-imagick/oldstable
--
php7.0/oldstable
--
phpmyadmin/oldstable
--
ruby-rails-admin/oldstable
--
ruby-rails-html-sanitizer/oldstable
--
ruby-zip/oldstable
--
salt/oldstable
--
sqlalchemy/oldstable
--
squid3/oldstable
--
tomcat7/oldstable
--
tomcat8/oldstable
--
------
The above is a list of DSA candidates based on the tracker's information.
One should evaluate the candidates and either add them to dsa-needed.txt
or consider tagging them no-dsa.
Reply to: