PAGES
← all tools
◆ Web Application Security

sslyze

6.3.0 open-source

Fast and powerful SSL/TLS scanning library.

Summary

sslyze is an open-source SSL/TLS scanning tool and Python library, free to use, and it is run as a command-line tool (installable via pip, Docker, or a precompiled Windows executable) or embedded directly into Python applications through its API. It connects to a server to check certificate validity, cipher suites, elliptic curves, and exposure to known TLS attacks like Heartbleed and ROBOT, checking results against Mozilla's recommended TLS profiles or a custom baseline. This suits application security engineers and developers who want TLS checks wired into CI/CD rather than run manually, and it covers non-HTTP protocols like SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. and LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. as well as HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate.. It sits in the TLS/certificate scanning category rather than broader web-app testing. First committed in 2011, it has 86 contributors and a release within the past five months, so it is actively maintained.

Fast and powerful SSL/TLS scanning library.

How sslyze helps

Will my server's certificate be trusted by the browsers and devices my users actually run?

validates the chain against five separate trust stores (Android, Apple, Java, Mozilla, Windows) and reports issuer, expiry, and structural problems like a missing subjectAltName that would cause silent trust failures on some platforms but not others

Is this server still open to known TLS attacks like Heartbleed or ROBOT?

actively probes for each named vulnerability (Heartbleed, ROBOT, OpenSSL CCS injection, insecure renegotiation, downgrade attacks) and reports vulnerable or not for each, rather than inferring risk from version numbers alone

Does this endpoint meet the TLS baseline my organization or Mozilla recommends?

runs the relevant scan commands automatically against Mozilla's old/intermediate/modern profiles, or against a custom baseline profile supplied as a file, and reports where the server's cipher suites, protocols, and curves fall short

Can I catch a TLS misconfiguration before it reaches production?

runs as a step in a CI/CD pipeline or is called through the Python API from application code, so a scan and compliance check happen automatically on every build rather than manually after deployment

Is my mail server or directory service exposed the same way my HTTPS servers are?

scans non-HTTP protocols like SMTP, XMPP, LDAP, POP, IMAP, RDP, Postgres and FTP using their own STARTTLS negotiation, giving the same certificate and cipher analysis outside of a browser context

Can I get a TLS reading on a server that's addressed only by IP, with no hostname?

retrieves the certificate chain even when no Server Name Indication is supplied, which matters for IP-only endpoints that would otherwise be skipped or misread by tools that require SNI

all 25 features, with the evidence for each →

Languages

Not documented

Features

25 capabilities · 10 backed by code, an API document or a real run

Built from sslyze's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • sslyze covers 1 of the 8 vulnerability assessment methods capabilities we track.

What sslyze offers you

  • Command-line interface12
  • Python scripting support3
  • Scripting language support2
  • CI/CD pipeline integration1
  • JSON data export1
  • Scripting API1
Web vulnerability scanning 4 features Vulnerability assessment methods since 2014
TLS compression detection verified Detects whether TLS compression is active on the server, a condition that makes it susceptible to CRIME-style attacks. 1 release · 2 other sources · first seen Sep 2014

Shared capability: Web vulnerability scanning

release

we ran it

  • TLS compression is disabled on the target. The certificate for tls.ctk.test is self-signed, valid until 2126-07-09, and fails trust validation across all five CA stores (Android, Apple, Java,… Aug 2026 · the full run

example

  • Check if the target server is vulnerable to the CRIME compression attack. sslyze --compression example.com 0.5.0 · Sep 2014 · source
HTTP header scanning shipped Scans a server's HTTP headers, including legacy HTTP Public Key Pinning (HPKP) information. 2 releases · 1 other source · first seen Sep 2016

Shared capability: Web vulnerability scanning

Also counts toward: Command-line interface

release

  • The CLI flag --hsts is renamed to --http_headers. Using --hsts will result in an error or unexpected behavior. 0.14.0 · Sep 2016 · source · release history
  • Renamed --hsts flag to --http_headers; this flag now returns HTTP Public Key Pinning (HPKP) information including HPKP header values and pins for each certificate in the verified chain. 0.14.0 · Sep 2016 · source · release history

example

  • Scan a server for HTTP headers (including legacy HPKP) using the new flag name. sslyze --http_headers ssl.example.com 0.14.0 · Sep 2016 · source
TLS downgrade attack detection verified Checks whether the server advertises support for TLS_FALLBACK_SCSV, which prevents attackers from forcing a weaker protocol version. 1 release · 1 other source · first seen Feb 2016

Shared capability: Web vulnerability scanning

Also counts toward: Command-line interface

release

  • Adds the --fallback command line flag to check support for the TLS_FALLBACK_SCSV cipher suite and prevent downgrade attacks 0.13.3 · Feb 2016 · source · release history

we ran it

  • The server supports TLS_FALLBACK_SCSV, so the downgrade-attack check passed. Aug 2026 · the full run
Programmatic ROBOT scanning API shipped Provides a class in the Python module for programmatic detection of the ROBOT vulnerability. 1 release · first seen Dec 2017

Shared capability: Web vulnerability scanning

Also counts toward: Python scripting support, Scripting API, Scripting language support

release

  • --robot flag added as a new capability for scanning servers against the ROBOT vulnerability 1.3.0 · Dec 2017 · source · release history
Other / not yet classified 21 features Features we have not matched to a capability yet. A suggested match is marked.
Mozilla TLS configuration compliance checking verified Checks whether the server's TLS settings match Mozilla's recommended configuration profiles or a custom profile supplied by the user. 12 releases · 11 other sources · first seen Sep 2014

Also counts toward: Command-line interface

release 12 total

  • Extends EllipticCurvesScanPlugin (the --elliptic_curves scan) to detect Brainpool curve support in addition to previously covered curves. 6.3.0 · Dec 2025 · source · release history
  • New check: detects whether the Extended Master Secret TLS extension is supported by the target server. 6.1.0 · Jan 2025 · source · release history
  • Adds Python 3.11 platform support 5.1.0 · Jan 2023 · source · release history
  • Adds --elliptic_curves detection of Brainpool curves 5.1.0 · Jan 2023 · source · release history
  • Adds support for more TLS stacks when connecting and scanning for elliptic curves 5.0.6 · Oct 2022 · source · release history
  • Disables server scan result checking against Mozilla configurations via --mozilla_config=disable 5.0.3 · Mar 2022 · source · release history

docs

  • Scans SSL/TLS server configurations to detect weak encryption settings and known TLS vulnerabilities.

command line

  • --custom_tls_config — Path to a JSON file containing a specific TLS configuration to check the server against, following Mozilla's format. Cannot be used with --mozilla_config. 6.2.0 · Aug 2025 · command-line history
  • --mozilla_config — Shortcut to queue various scan commands needed to check the server's TLS configurations against one of Mozilla's recommended TLS configuration. Set to "intermediate" by default. 5.0.1 · Dec 2021 · command-line history

we ran it

  • Despite --quiet being set, the run printed a compliance notice that TLS configuration checking is disabled without a --mozilla_config or --custom_tls_config flag, plus a… Aug 2026 · the full run

example 7 total

  • Scan a server for support of Brainpool elliptic curves. sslyze --regular example.com --elliptic_curves 5.1.0 · Jan 2023 · source
  • Identify which elliptic curves a target server accepts or rejects to assess key exchange security posture. python -m sslyze --elliptic_curves www.cloudflare.com 3.1.0 · Nov 2020 · source
  • Scan a server to verify official TLS 1.3 support using the new flag python -m sslyze --tls_1_3 www.cloudflare.com 2.0.0 · Sep 2018 · source
  • Limit retry attempts to reduce scan duration or avoid timeouts on unstable servers. sslyze my-server.com --nb_retries 3 0.8.0 · Sep 2014 · source
  • Check if a server is affected by Chrome's deprecation of SHA1-signed certificates sslyze --chrome_sha1 server.example.com:443 0.10.0 · Sep 2014 · source
  • Check compliance against Mozilla modern config python -m sslyze --mozilla_config=modern mozilla.com
Certificate trust store validation verified Validates the server's certificate against the Android, Apple, Java, Mozilla, and Windows trust stores, and reports any that reject it and the reason why. 6 releases · 5 other sources · first seen Sep 2014

release

  • Added the OpenJDK trust store when validating the server's certificate. 2.0.2 · Dec 2018 · source · release history
  • Adds --update_trust_stores CLI flag to update the local trust stores repository. 1.3.4 · Feb 2018 · source · release history
  • Adds the Android Open Source Project's trust store when using --certinfo 0.13.6 · Jun 2016 · source · release history
  • Added Google trust store for certificate validation 0.12.0 · Sep 2015 · source · release history
  • --ca_file allows specifying a local trust store for certificate validation. 0.11.0 · Apr 2015 · source · release history
  • Extends certificate chain validation to Apple, Microsoft, and Java trust stores alongside Mozilla's 0.8.0 · Sep 2014 · source · release history

we ran it

  • The self-signed certificate for tls.ctk.test fails trust validation across all five CA stores (Android, Apple, Java, Mozilla, Windows) because it lacks a subjectAltName extension, and OCSP stapling… Aug 2026 · the full run
  • The server supports TLS_FALLBACK_SCSV, so the downgrade-attack check passed. Aug 2026 · the full run

example

  • Update SSLyze's local trust store definitions via the command line. sslyze --update_trust_stores 1.3.4 · Feb 2018 · source
  • Validate a server's certificates against the AOSP trust store. sslyze --certinfo=scan_commands server.example.com:443 0.13.6 · Jun 2016 · source
  • Scan an RDP server using StartTLS to validate its certificate against multiple OS-specific trust stores. sslyze --starttls=rdp my-rdp-server.com 0.8.0 · Sep 2014 · source
JSON result export and parsing shipped Serializes scan results to JSON and provides a helper class to parse those results in a separate Python program. 7 releases · 3 other sources · first seen Sep 2014

Also counts toward: JSON data export, Python scripting support

release 7 total

  • Auto-generated JSON schema available at ./json_output_schema.json 5.0.0 · Nov 2021 · source · release history
  • Fully-typed Python API for parsing JSON output using SslyzeOutputAsJson.parse_file 5.0.0 · Nov 2021 · source · release history
  • --certinfo command now returns OCSPMustStaple and CertificateTransparency extension data in JSON/XML output 1.3.0 · Dec 2017 · source · release history
  • Adds Subject and Issuer fields to the XML output 1.1.3 · Sep 2017 · source · release history
  • The --print_full_certificate option is no longer available; XML/JSON consumers must parse the PEM-formatted certificate in the output using their own libraries. 1.1.0 · Apr 2017 · source · release history
  • Adds --json_out command for writing results to a file as JSON. 0.13.4 · Feb 2016 · source · release history

docs

  • Exporting and processing scan results in JSON The result of SSLyze scans can be serialized to JSON for further processing. SSLyze also provides a helper class to parse JSON scan results; it can be used to process the results of SSLyze scans in a separate Python program. docs update · Oct 2026 · source

example

  • Parse a previously run SSLyze JSON result file using the new typed Python API. parsed_json_result = SslyzeOutputAsJson.parse_file("result.json") 5.0.0 · Nov 2021 · source
  • Write the full SSL/TLS scan output to a local file for downstream parsing or logging. sslyze --json_out /tmp/scan_results.json tls://example.com:443 0.13.4 · Feb 2016 · source
Certificate chain analysis verified Retrieves and reports the server's certificate chain, including key type, key size, validity dates, self-signed status, and how many chains were detected. 5 releases · 4 other sources · first seen Sep 2014

release

  • Adds certificate validation for Subject Alternative Names containing IP addresses 5.1.0 · Jan 2023 · source · release history
  • --resum_attempts option to configure session resumption attempts (default 5) 5.0.0 · Nov 2021 · source · release history
  • The --certinfo_basic command is renamed to --certinfo. 1.0.0 · Feb 2017 · source · release history
  • --certinfo_basic now returns the server's verified certificate chain (leaf to Mozilla root) when the server's certificate is trusted. 0.14.0 · Sep 2016 · source · release history
  • PluginCertInfo now displays the server's full certificate chain instead of its leaf certificate only, in both the console and XML results 0.10.0 · Sep 2014 · source · release history

we ran it

  • One RSA 2048-bit certificate chain for tls.ctk.test, self-signed and failing trust validation across all five CA stores (Android, Apple, Java, Mozilla, Windows) due to a missing subjectAltName… Aug 2026 · the full run
  • One RSA 2048-bit certificate chain was detected, self-signed by tls.ctk.test with a validity window of 2026-08-02 to 2126-07-09. Aug 2026 · the full run

example

  • Configure session resumption testing to attempt 20 resumptions instead of the default. python -m sslyze --resum --resum_attempts=20 www.google.com 5.0.0 · Nov 2021 · source
  • Retrieve the full verified certificate chain for a trusted server using the enhanced basic certinfo command. sslyze --certinfo_basic ssl.example.com 0.14.0 · Sep 2016 · source
Python module integration shipped Makes the cyber tool importable as a Python module for programmatic use in scripts. 8 releases · 1 other source · first seen Feb 2016

Also counts toward: Python scripting support, Scripting language support

release 8 total

  • Enables supplying a custom HTTP agent via the Python API for HTTPS scanning. 6.1.0 · Jan 2025 · source · release history
  • Enables configuring the number of client renegotiation test attempts via the Python API. 6.1.0 · Jan 2025 · source · release history
  • Enables supplying a custom SMTP EHLO hostname via the Python API for STARTTLS scanning. 6.1.0 · Jan 2025 · source · release history
  • Added more precise exceptions when the ServerConnectivityTester fails to connect to the server. 2.0.2 · Dec 2018 · source · release history
  • Python API now returns specialized subclasses of ServerConnectivityError for specific connectivity testing failures. 1.4.0 · Mar 2018 · source · release history
  • Adds TrustStoresRepository.update_default() method to the Python API for trust store updates. 1.3.4 · Feb 2018 · source · release history

example

  • Programmatically refresh trust stores within a Python script using the API. from sslyze import TrustStoresRepository TrustStoresRepository.update_default() 1.3.4 · Feb 2018 · source
OCSP stapling and Must-Staple checking verified Checks whether the server staples an OCSP response and whether the certificate carries the Must-Staple extension requiring it to do so. 2 releases · 2 other sources · first seen Sep 2014

Also counts toward: Command-line interface

release

  • CertificateInfoScanCommand now displays certificate transparency SCTs when available via OCSP Stapling 1.1.0 · Apr 2017 · source · release history
  • Adds --certinfo option to retrieve and display OCSP Stapling status for tested endpoints. 0.7.0 · Sep 2014 · source · release history

we ran it

  • The output is truncated. The certificate for tls.ctk.test is self-signed, valid until 2126, and fails trust validation against all five CA stores (Android, Apple, Java, Mozilla, Windows) due to a… Aug 2026 · the full run
  • The self-signed RSA-2048 certificate for tls.ctk.test fails trust validation across all five CA stores (Android, Apple, Java, Mozilla, Windows) due to a missing subjectAltName extension, and lacks… Aug 2026 · the full run
TLS 1.3 early data detection verified suggested Determines whether the server accepts TLS 1.3 early data, which can allow an attacker to replay previously captured requests. 2 releases · 2 other sources · first seen Dec 2017

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Added --early_data flag and EarlyDataScanCommand for beta TLS 1.3 early data (0-RTT) testing 2.0.0 · Sep 2018 · source · release history
  • Improved speed when testing for TLS 1.3 cipher suites using --tlsv1_3. 1.3.2 · Dec 2017 · source · release history

we ran it

  • The self-signed RSA-2048 certificate (CN=tls.ctk.test, valid until 2126) fails trust validation across all five CA stores because it lacks a subjectAltName extension, and OCSP stapling and… Aug 2026 · the full run

example

  • Test a server for TLS 1.3 early data (0-RTT) support using the new beta flag python -m sslyze --early_data www.cloudflare.com 2.0.0 · Sep 2018 · source
Pre-compiled executable distribution shipped Distributes a standalone executable to allow use without installing the Python runtime on Windows. 4 releases · first seen Sep 2017

release

CI/CD integration output shipped Enables streaming scan results to stdout in XML format for piping into continuous integration pipelines. 3 releases · 1 other source · first seen Apr 2015

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Ability to run as a CI/CD step via the README instructions 5.0.0 · Nov 2021 · source · release history
  • --xml_out - enables printing XML output directly to the console instead of a file 0.12.0 · Sep 2015 · source · release history
  • The XML output format changed in a way that breaks parsing by existing tools; an XML Schema Definition is now provided to align consumers. 0.11.0 · Apr 2015 · source · release history

example

  • Stream sslyze XML results to stdout for piping into other tools in a CI pipeline. sslyze --regular example.com --xml_out - 0.12.0 · Sep 2015 · source
Concurrent connection control shipped suggested Limits the number of simultaneous connections to prevent overloading the target server. 3 releases · 1 other source · first seen Sep 2014

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Replaces --timeout and --nb_retries CLI options with a new --slow_connection argument to handle slow servers or limited concurrency. 1.4.0 · Mar 2018 · source · release history
  • The --timeout and --nb_retries CLI options are removed; use --slow_connection instead. 1.4.0 · Mar 2018 · source · release history
  • Introduces a hard cap on concurrent connections (approx. 30 per server) via internal logic to prevent target overload 0.9.0 · Sep 2014 · source · release history

example

  • Limit retry attempts to reduce scan duration or avoid timeouts on unstable servers. sslyze my-server.com --nb_retries 3 0.8.0 · Sep 2014 · source
StartTLS protocol scanning shipped Scans non-SSL/TLS protocols (RDP, FTP, POP, IMAP, LDAP) by establishing a StartTLS handshake first. 4 releases · first seen Sep 2014

Also counts toward: Command-line interface

release

  • Support for supplying a full (client) certificate chain when authenticating with client certificates 0.12.0 · Sep 2015 · source · release history
  • Added support for Postgres StartTLS. 0.11.0 · Apr 2015 · source · release history
  • Adds --starttls=rdp flag to enable StartTLS RDP scanning 0.8.0 · Sep 2014 · source · release history
  • Adds --starttls flag to scan FTP, POP, IMAP, LDAP, and auto protocols, removing the requirement for plain SSL/TLS connections. 0.7.0 · Sep 2014 · source · release history
Custom policy compliance checking shipped Validates server configurations against custom policies or baseline profiles instead of only Mozilla presets. 1 release · 2 other sources · first seen Aug 2025

release

  • Supports specifying a custom TLS configuration/profile to validate servers against, as an alternative to the built-in Mozilla old/intermediate/modern profiles. 6.2.0 · Aug 2025 · source · release history

example

  • Audit a server against your own TLS policy (e.g. org-wide cipher/protocol baseline) instead of a Mozilla preset. sslyze --custom_tls_config <path_to_config> <target> 6.2.0 · Aug 2025 · source
  • Check against custom TLS configuration file python -m sslyze --custom_tls_config custom_tls_config_example.json mozilla.com
Heartbleed vulnerability detection shipped Tests the server for the Heartbleed OpenSSL vulnerability. 2 releases · 1 other source · first seen Sep 2014

Also counts toward: Command-line interface

release

  • Adds the --openssl_ccs command line flag to check for the OpenSSL CCS Injection vulnerability 0.13.3 · Feb 2016 · source · release history
  • Adds --heartbleed flag to enable experimental Heartbleed vulnerability detection, also included in regular scans 0.9.0 · Sep 2014 · source · release history

example

  • Scan for Heartbleed vulnerability on a specific host sslyze --heartbleed <target> 0.9.0 · Sep 2014 · source
Batch target scanning shipped Scans multiple servers defined in a text file rather than passing them individually as arguments. 1 release · 2 other sources · first seen Sep 2014

release

  • Introduces a hard cap on concurrent connections (approx. 30 per server) via internal logic to prevent target overload 0.9.0 · Sep 2014 · source · release history

example

  • Scan a batch of servers defined in a file instead of passing them as individual arguments. sslyze --targets_in targets.txt 0.5.0 · Sep 2014 · source
  • Scan multiple servers including IPv6 python -m sslyze www.yahoo.com www.google.com "[2607:f8b0:400a:807::2004]:443"
Certificate Transparency checking verified Checks whether the server's certificate includes Certificate Transparency information demonstrating it has been logged to a public CT log. 2 other sources · first seen Aug 2026

we ran it

  • The self-signed RSA-2048 certificate (CN=tls.ctk.test, valid until 2126) fails trust validation across all five CA stores because it lacks a subjectAltName extension, and OCSP stapling and… Aug 2026 · the full run
  • The self-signed RSA 2048-bit certificate (CN=tls.ctk.test, valid until 2126) fails trust validation across all five CA stores checked — Android, Apple, Java, Mozilla, and Windows — because it lacks a… Aug 2026 · the full run
ROBOT vulnerability checking verified suggested Tests whether the server is vulnerable to ROBOT, a class of attack that can allow an adversary to decrypt RSA-encrypted traffic by exploiting a padding oracle. 2 other sources · first seen Dec 2017

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

we ran it

  • The ROBOT check returned not vulnerable. Certificate analysis found one RSA 2048-bit chain issued by tls.ctk.test, self-signed and untrusted across all five CA stores (Android, Apple, Java, Mozilla,… Aug 2026 · the full run

example

  • Quickly check if a public server is vulnerable to the ROBOT attack via CLI. sslyze --robot www.google.com 1.3.0 · Dec 2017 · source
Non-SNI certificate retrieval shipped Retrieves the certificate chain from servers that do not support or require Server Name Indication (SNI). 1 release · 1 other source · first seen Aug 2025

Also counts toward: Command-line interface

release

  • Supports retrieving a server's certificate chain when no Server Name Indication (SNI) is supplied via --certinfo. 6.2.0 · Aug 2025 · source · release history

example

  • Retrieve the certificate chain presented by a server that doesn't support or require SNI — useful for IP-only TLS endpoints. sslyze --certinfo <target> 6.2.0 · Aug 2025 · source
Standard scan profile shipped Runs a predefined set of SSL/TLS checks as the default operation without requiring explicit scan flags. 1 release · 1 other source · first seen Jun 2020

release

  • python -m sslyze google.com now runs --regular by default instead of requiring explicit scan options 3.0.7 · Jun 2020 · source · release history

example

  • Quickly run a standard set of SSL/TLS tests on a target without typing extra flags. python -m sslyze google.com 3.0.7 · Jun 2020 · source
HTTPS proxy tunneling shipped Tunnels scan traffic through an HTTPS proxy that requires Basic Authentication. 1 release · 1 other source · first seen Sep 2014

Also counts toward: Command-line interface

release

  • Adds support for Basic Authentication when using --https_tunnel by parsing credentials from the proxy URL 0.9.0 · Sep 2014 · source · release history

example

  • Tunnel a scan through an HTTPS proxy requiring Basic Authentication sslyze --https_tunnel=http://user:password@proxy.example.com:8080 <target> 0.9.0 · Sep 2014 · source
Target input validation verified Validates each scan target and rejects inputs that are not in bare hostname or host:port format, such as full URLs that include a scheme. 1 other source · first seen Aug 2026

we ran it

  • The tool rejected the target immediately, reporting Not a valid host:port; discarding scan because sslyze expects a bare hostname or host:port rather than a URL with a scheme. Aug 2026 · the full run
Client authentication (mTLS) cipher suite scanning shipped Scans cipher suites on servers that require client certificates for mutual TLS authentication. 1 release · first seen Apr 2017

release

  • Added support for scanning cipher suites on servers that require client authentication (mutual TLS) 1.1.0 · Apr 2017 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for sslyze, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail sslyze puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

36 entries

  1. October 20261
  2. December 20251
  3. August 20251
  4. January 20251
  5. September 20231
  6. April 20231
  7. January 20231
  8. October 20221
  9. March 20221
  10. November 20211
  11. November 20201
  12. June 20201
  13. April 20201
  14. December 20181
  15. September 20181
  16. March 20181
  17. February 20181
  18. December 20172
  19. November 20171
  20. September 20171
  21. April 20171
  22. February 20171
  23. October 20161
  24. September 20161
  25. June 20161
  26. February 20162
  27. September 20151
  28. April 20151
  29. September 20146
    Show

    36 entries

    Project health

    Issue, contributor and maintainer activity in nabla-c0d3/sslyze, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 2 −5 vs prior 12 months
    2. Maintainers 1 +0 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 83% of issues opened, last 12 months
    5. Median time to close 131 days first maintainer reply 7.2 days
    6. Open backlog 24 of 557 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 24
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 3,781
    Issue themes, last 12 months
    • bugs 8%
    • other 92%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →