Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-07 02:20 UTC

tls-attacker / TLS-Attacker

TLS-Attacker is a Java-based framework for analyzing TLS libraries. It can be used to manually test TLS clients and servers or as as a software library for more advanced tools.

JavaApache-2.0★ 880 stars⑂ 147 forkssince Apr 2016View on GitHub ↗

tls-attacker/TLS-Attacker holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Security (42/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

69
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

69
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 62 is calibrated to 69 on the published index scale (record calibration 2026-08-02).

Ownership

TLS-AttackerOrganization
59 followers42 public repossince Feb 2019

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavende.rub.nds.tls.attacker:utils7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:tls-core7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:tls-mitm7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:tls-proxy7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:trace-tool7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:transport7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:tls-client7.8.0-2637 days ago
Mavende.rub.nds.tls.attacker:tls-server7.8.0-2637 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
25.6/36Commit cadence37/52 weeks with commits
18/18Commit volume296 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year296
human_commit_share0.98
days_since_last_push1
active_weeks_last_year37
How it's scored
27/27Ships releases42 releases published
36/36Release recencylatest release 37 days ago
12.6/27Release cadencea release every ~124.4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count42
latest_release_tagv7.0.0-rtc
releases_from_tagsno
days_since_latest_release37
mean_days_between_releases124.4

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

63Moderate · 17% of overall
How it's scored
47.8/60Stars880 stars
18/25Forks147 forks
9.5/15Watchers52 watchers
Inputs used
forks147
stars880
watchers52
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11.1/22.5Commit distributiontop contributor authored 51% of commits
13.5/13.5Contributor breadth92 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled92
top_contributor_share0.506
How it's scored
36.2/42Issue resolution86% of issues closed
9/30PR acceptance22/73 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs22
open_issues22
closed_issues137
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.862
closed_unmerged_prs51
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
12.8/25Owner reach59 followers of tls-attacker
23.9/25Track record42 public repos, account ~7 yr old
Inputs used
followers59
owner_typeOrganization
is_verifiedno
owner_logintls-attacker
public_repos42
account_age_days2,770

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on maven
35/35Publish recencylatest publish 37 days ago
20/20Version history26 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesde.rub.nds.tls.attacker:utils, de.rub.nds.tls.attacker:tls-core, de.rub.nds.tls.attacker:tls-mitm, de.rub.nds.tls.attacker:tls-proxy, de.rub.nds.tls.attacker:trace-tool, de.rub.nds.tls.attacker:transport, de.rub.nds.tls.attacker:tls-client, de.rub.nds.tls.attacker:tls-server
ecosystemsmaven
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 10 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities19 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Packaging. Remaining weights renormalized.
How it's scored
11/35Direct dependencies free of known advisories4 affected: org.bouncycastle:bcprov-jdk18on 1.81 (high 7.7), org.bouncycastle:bcpkix-jdk18on 1.81 (moderate 5.3), org.apache.logging.log4j:log4j-api 2.25.1 (low), +1 more
6.8/25Indirect dependencies free of known advisories3 affected: com.fasterxml.jackson.core:jackson-core 2.19.1 (high 7.5), com.fasterxml.jackson.core:jackson-databind 2.19.1 (high 8.1), junit:junit 4.10 (moderate 4.4)
23.3/40No advisories left outstanding5 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,155 days ago
Inputs used
sourceosv
advisories16
affected_packages7
assessed_packages45
unassessed_packages0
affected_by_severityhigh 3, moderate 2, low 2
direct_affected_packages4
Matched the maven:de.rub.nds.tls.attacker:utils@7.8.0 runtime dependency closure — what installing the published package pulls in — 45 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

55Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
12/40Legible commit history22 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.224
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapTLS-Client/pom.xml, TLS-Core/pom.xml, TLS-Mitm/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingJava (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsTLS-Client/pom.xml, TLS-Core/pom.xml, TLS-Mitm/pom.xml, TLS-Proxy/pom.xml, TLS-Server/pom.xml, TraceTool/pom.xml, Transport/pom.xml, Utils/pom.xml, pom.xml
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable codeJava (statically typed)
54.8/55Manageable file sizes7/2,086 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes178,992
source_files_sampled2,086
oversized_source_files7
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

880GitHub stars
92contributors
296commits, last 12 months
1days since last push
42releases
1bus factor
22open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 147 ⇿
0Stars
147Forks
41Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0255075100125150145112016-042021-062026-08
Major 0Minor 8Patch 14

Each point covers 10 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-07 02:20 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities19 existing vulnerabilities detected
Direct dependencies 39
RegistryPackageVersion constraintManifest
Maven${project.groupId}:tls-coreTLS-Client/pom.xml
Maven${project.groupId}:transportTLS-Client/pom.xml
Maven${project.groupId}:utilsTLS-Client/pom.xml
Maven${project.groupId}:transportTLS-Core/pom.xml
Maven${project.groupId}:utilsTLS-Core/pom.xml
Maven${project.groupId}:tls-coreTLS-Mitm/pom.xml
Maven${project.groupId}:utilsTLS-Mitm/pom.xml
Maven${project.groupId}:tls-coreTLS-Proxy/pom.xml
Maven${project.groupId}:transportTLS-Proxy/pom.xml
Maven${project.groupId}:tls-coreTLS-Server/pom.xml
Maven${project.groupId}:tls-coreTraceTool/pom.xml
Maven${project.groupId}:utilsTransport/pom.xml
Mavende.rub.nds.tls.attacker:tls-attacker${project.version}pom.xml
Mavende.rub.nds.tls.attacker:tls-client${project.version}pom.xml
Mavende.rub.nds.tls.attacker:tls-core${project.version}pom.xml
Mavende.rub.nds.tls.attacker:tls-mitm${project.version}pom.xml
Mavende.rub.nds.tls.attacker:tls-proxy${project.version}pom.xml
Mavende.rub.nds.tls.attacker:tls-server${project.version}pom.xml
Mavende.rub.nds.tls.attacker:trace-tool${project.version}pom.xml
Mavende.rub.nds.tls.attacker:transport${project.version}pom.xml
Mavende.rub.nds.tls.attacker:utils${project.version}pom.xml
Mavencom.beust:jcommanderpom.xml
Mavencom.google.guava:guavapom.xml
Mavencom.googlecode.json-simple:json-simplepom.xml
Mavende.rub.nds:asn1-attacker4.2.3pom.xml
Mavende.rub.nds:modifiable-variable5.3.0pom.xml
Mavende.rub.nds:protocol-attacker2.2.2pom.xml
Mavende.rub.nds:x509-attacker4.3.10pom.xml
Mavendnsjava:dnsjavapom.xml
Mavenjakarta.xml.bind:jakarta.xml.bind-apipom.xml
Mavenorg.apache.commons:commons-lang3pom.xml
Mavenorg.apache.logging.log4j:log4j-apipom.xml
Mavenorg.apache.logging.log4j:log4j-corepom.xml
Mavenorg.apache.logging.log4j:log4j-slf4j-implpom.xml
Mavenorg.bouncycastle:bcpkix-jdk18onpom.xml
Mavenorg.bouncycastle:bcprov-jdk18onpom.xml
Mavenorg.cryptomator:siv-modepom.xml
Mavenorg.glassfish.jaxb:jaxb-runtimepom.xml
Mavenorg.reflections:reflectionspom.xml
All dependencies 50

Full resolved dependency set from the GitHub dependency graph: 27 direct and 23 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Mavencom.beust:jcommanderdirect
Mavencom.google.guava:guavadirect
Mavencom.googlecode.json-simple:json-simpledirect
Mavende.rub.nds.tls.attacker:tls-attacker7.8.0direct
Mavende.rub.nds.tls.attacker:tls-client7.8.0direct
Mavende.rub.nds.tls.attacker:tls-core7.8.0direct
Mavende.rub.nds.tls.attacker:tls-mitm7.8.0direct
Mavende.rub.nds.tls.attacker:tls-proxy7.8.0direct
Mavende.rub.nds.tls.attacker:tls-server7.8.0direct
Mavende.rub.nds.tls.attacker:trace-tool7.8.0direct
Mavende.rub.nds.tls.attacker:transport7.8.0direct
Mavende.rub.nds.tls.attacker:utils7.8.0direct
Mavende.rub.nds:asn1-attacker4.2.3direct
Mavende.rub.nds:modifiable-variable5.3.0direct
Mavende.rub.nds:protocol-attacker2.2.2direct
Mavende.rub.nds:x509-attacker4.3.10direct
Mavendnsjava:dnsjavadirect
Mavenjakarta.xml.bind:jakarta.xml.bind-apidirect
Mavenorg.apache.commons:commons-lang3direct
Mavenorg.apache.logging.log4j:log4j-apidirect
Mavenorg.apache.logging.log4j:log4j-coredirect
Mavenorg.apache.logging.log4j:log4j-slf4j-impldirect
Mavenorg.bouncycastle:bcpkix-jdk18ondirect
Mavenorg.bouncycastle:bcprov-jdk18ondirect
Mavenorg.cryptomator:siv-modedirect
Mavenorg.glassfish.jaxb:jaxb-runtimedirect
Mavenorg.reflections:reflectionsdirect
Mavencom.diffplug.spotless:spotless-maven-pluginindirect
Mavencom.github.spotbugs:spotbugs-maven-pluginindirect
Mavencom.openpojo:openpojoindirect
Mavende.rub.nds.tls.dockerlib:tls-docker-library3.2.2indirect
Mavenorg.apache.maven.plugins:maven-clean-pluginindirect
Mavenorg.apache.maven.plugins:maven-compiler-pluginindirect
Mavenorg.apache.maven.plugins:maven-dependency-pluginindirect
Mavenorg.apache.maven.plugins:maven-dependency-plugin7.8.0indirect
Mavenorg.apache.maven.plugins:maven-deploy-pluginindirect
Mavenorg.apache.maven.plugins:maven-failsafe-pluginindirect
Mavenorg.apache.maven.plugins:maven-jar-pluginindirect
Mavenorg.apache.maven.plugins:maven-javadoc-pluginindirect
Mavenorg.apache.maven.plugins:maven-jxr-pluginindirect
Mavenorg.apache.maven.plugins:maven-pmd-pluginindirect
Mavenorg.apache.maven.plugins:maven-resources-pluginindirect
Mavenorg.apache.maven.plugins:maven-source-pluginindirect
Mavenorg.apache.maven.plugins:maven-surefire-pluginindirect
Mavenorg.codehaus.mojo:flatten-maven-pluginindirect
Mavenorg.jacoco:jacoco-maven-pluginindirect
Mavenorg.junit.jupiter:junit-jupiterindirect
Mavenorg.junit.platform:junit-platform-launcherindirect
Mavenorg.mockito:mockito-coreindirect
Mavenorg.mockito:mockito-junit-jupiterindirect
Dependency advisories 7

Installing maven:de.rub.nds.tls.attacker:utils@7.8.0 pulls in 45 packages, direct and transitive: 7 carry known advisories, of which 4 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
org.bouncycastle:bcprov-jdk18on1.81directhigh21.84
com.fasterxml.jackson.core:jackson-core2.19.1indirecthigh23.1.4
com.fasterxml.jackson.core:jackson-databind2.19.1indirecthigh53.1.4
org.bouncycastle:bcpkix-jdk18on1.81directmoderate11.84
junit:junit4.10indirectmoderate14.13.1
org.apache.logging.log4j:log4j-api2.25.1directlow12.26.1
org.apache.logging.log4j:log4j-core2.25.1directlow42.25.4

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsMaven.