Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 00:55 UTC

tslearn-team / tslearn

The machine learning toolkit for time series analysis in Python

PythonBSD-2-Clause★ 3,168 stars⑂ 373 forkssince May 2017View on GitHub ↗

tslearn-team/tslearn holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (88/100) and lowest on AI Readiness (52/100). It was last updated today. A single contributor accounts for most of its recent work.

90
overall / 100
Excellent

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.

90
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 76 is calibrated to 90 on the published index scale (record calibration 2026-08-02).

Ownership

tslearn-teamOrganization
37 followers4 public repossince Apr 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPItslearn0.9.0274,8328541 days ago

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
24.9/36Commit cadence — 36/52 weeks with commits
18/18Commit volume — 102 commits in the last year
10/10OpenSSF Scorecard: Maintained — 19 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year102
human_commit_share0.96
days_since_last_push0
active_weeks_last_year36
How it's scored
27/27Ships releases — 26 releases published
36/36Release recency — latest release 43 days ago
12.6/27Release cadence — a release every ~139.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tagv0.9.0
releases_from_tagsno
days_since_latest_release43
mean_days_between_releases139.6
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

88Excellent · 17% of overall
How it's scored
56.8/60Stars — 3,168 stars
21.4/25Forks — 373 forks
9.7/15Watchers — 57 watchers
Inputs used
forks373
stars3,168
watchers57
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, codecov.io, dev.azure.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
72.5/80Monthly downloads — 274,832 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestslearn
dependents
ecosystemspypi
total_downloads
monthly_downloads274,832
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.4/22.5Commit distribution — top contributor authored 67% of commits
13.5/13.5Contributor breadth — 42 contributors
10/10OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled42
top_contributor_share0.672
How it's scored
33.5/42Issue resolution — 80% of issues closed
23.4/30PR acceptance — 243/312 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/26 approved changesets -- score normalized to 0
Inputs used
merged_prs243
open_issues68
closed_issues269
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d7
issue_closed_ratio0.798
closed_unmerged_prs69
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
11.4/25Owner reach — 37 followers of tslearn-team
17.1/25Track record — 4 public repos, account ~6 yr old
Inputs used
followers37
owner_typeOrganization
is_verified
owner_logintslearn-team
public_repos4
account_age_days2,296
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 41 days ago
20/20Version history — 85 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestslearn
ecosystemspypi
any_deprecatedno
min_days_since_publish41

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 24 out of 24 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://tslearn.readthedocs.io
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicstime-series, timeseries, time-series-analysis, time-series-clustering, machine-learning, machine-learning-algorithms, machinelearning, dtw, python, time-series-classification, dynamic-time-warping
has_wikiyes
homepagehttps://tslearn.readthedocs.io
docs_sitehttps://tslearn.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 2/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 20 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 19 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages14
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:tslearn@0.9.0 runtime dependency closure — what installing the published package pulls in — 14 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
37.8/40Legible commit history — 68 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.708
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.04
How it's scored
0/45Type-checkable code — Python without a type-check config
45.9/55Manageable file sizes — 23/139 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes453,560
source_files_sampled139
oversized_source_files23
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

3,168GitHub stars
42contributors
102commits, last 12 months
0days since last push
26releases
1bus factor
68open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 373 ⇿
0Stars
373Forks
26Releases

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.

012525037536752017-062021-122026-07
Major 0Minor 6Patch 12

Each point covers 9 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-08-13 00:54 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/26 approved changesets -- score normalized to 0
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained19 commit(s) and 1 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIscikit-learn>=1.5pyproject.toml
PyPInumpy>=1.24.3pyproject.toml
PyPIscipy>=1.10.1pyproject.toml
PyPInumba>=0.61pyproject.toml
PyPIjoblib>=1.2pyproject.toml
PyPIstatsmodels>=0.14pyproject.toml
All dependencies 56

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

RegistryPackageVersionRelation
PyPIjoblibdirect
PyPIjoblib1.5.3direct
PyPInumbadirect
PyPInumba0.65.0direct
PyPInumpydirect
PyPInumpy2.4.4direct
PyPIscikit-learndirect
PyPIscikit-learn1.8.0direct
PyPIscipydirect
PyPIscipy1.17.1direct
PyPIstatsmodelsdirect
PyPIaccessible-pygments0.0.5indirect
PyPIalabaster1.0.0indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.14.3indirect
PyPIcertifi2026.2.25indirect
PyPIcharset-normalizer3.4.7indirect
PyPIcontourpy1.3.3indirect
PyPIcycler0.12.1indirect
PyPIdocutils0.22.4indirect
PyPIfonttools4.62.1indirect
PyPIidna3.15indirect
PyPIimagesize2.0.0indirect
PyPIjinja23.1.6indirect
PyPIkerasindirect
PyPIkiwisolver1.5.0indirect
PyPIllvmlite0.47.0indirect
PyPImarkupsafe3.0.3indirect
PyPImatplotlib3.10.8indirect
PyPInumpydoc1.10.0indirect
PyPIpackaging26.1indirect
PyPIpillow12.3.0indirect
PyPIpydata-sphinx-theme0.17.0indirect
PyPIpygments2.20.0indirect
PyPIpypandoc1.17indirect
PyPIpyparsing3.3.2indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIrequests2.33.1indirect
PyPIroman-numerals4.1.0indirect
PyPIsetuptoolsindirect
PyPIsetuptools-scmindirect
PyPIsix1.17.0indirect
PyPIsnowballstemmer3.0.1indirect
PyPIsoupsieve2.8.4indirect
PyPIsphinx9.1.0indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinx-gallery0.20.0indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIthreadpoolctl3.6.0indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
Dependency advisories 0

Installing pypi:tslearn@0.9.0 pulls in 14 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.31.0 — full methodology · metrics wiki.

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