Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-20 14:26 UTC

IBM / ibm-cos-sdk-python-s3transfer

ibm-cos-sdk-python-s3transfer

PythonApache-2.0★ 1 star⑂ 5 forkssince Sep 2017View on GitHub ↗

IBM/ibm-cos-sdk-python-s3transfer holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (66/100) and lowest on Security (21/100). It was last updated 220 days ago. A single contributor accounts for most of its recent work.

44
overall / 100
Weak

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.

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

Ownership

International Business MachinesOrganization · verified domain
9,055 followers2,732 public repossince Feb 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIibm-cos-sdk-s3transfer2.16.21,461,11655220 days ago

Metrics by category

Vitality

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

38Weak · 21% of overall
How it's scored
3.6/36Push recency — last push 220 days ago
3.5/36Commit cadence — 5/52 weeks with commits
7/18Commit volume — 5 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year5
human_commit_share0.99
days_since_last_push220
active_weeks_last_year5
How it's scored
27/27Ships releases — 55 releases published
16.2/36Release recency — latest release 220 days ago
19.8/27Release cadence — a release every ~74.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count55
latest_release_tag2.16.2
releases_from_tagsno
days_since_latest_release220
mean_days_between_releases74.6

Community & Adoption

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

46Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
5/25Forks — 5 forks
4.7/15Watchers — 8 watchers
Inputs used
forks5
stars1
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 1,461,116 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesibm-cos-sdk-s3transfer
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,461,116
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.8/22.5Commit distribution — top contributor authored 65% of commits
13.5/13.5Contributor breadth — 19 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.654
How it's scored
37.3/42Issue resolution — 89% of issues closed
0/30PR acceptance — 0/2 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs0
open_issues1
closed_issues8
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.889
closed_unmerged_prs2
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
20/20Verified domain
25/25Owner reach — 9,055 followers of IBM
25/25Track record — 2,732 public repos, account ~14 yr old
Inputs used
followers9,055
owner_typeOrganization
is_verifiedyes
owner_loginIBM
public_repos2,732
account_age_days5,385
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
26/35Publish recency — latest publish 220 days ago
20/20Version history — 55 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesibm-cos-sdk-s3transfer
ecosystemspypi
any_deprecatedno
min_days_since_publish220

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — setup.cfg ([flake8]), tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

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?

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsrequirements-dev.txt, requirements-test.txt, setup.cfg, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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_packages9
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:ibm-cos-sdk-s3transfer@2.16.2 runtime dependency closure — what installing the published package pulls in — 9 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.5/40Legible commit history — 12 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.121
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — setup.cfg ([flake8]), tox.ini
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/53 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes42,396
source_files_sampled53
oversized_source_files0

Key facts

1GitHub stars
19contributors
5commits, last 12 months
220days since last push
55releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/IBM/ibm-cos-sdk-python-s3transfer: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/IBM/ibm-cos-sdk-python-s3transfer/legacy.tar.gz/refs/heads/master": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
39Releases

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.

1223344412018-032021-042024-05
Major 0Minor 14Patch 25

Each point covers 6 days.

All dependencies 13

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

RegistryPackageVersionRelation
PyPIatomicwrites—indirect
PyPIcolorama—indirect
PyPIcoverage7.13.1indirect
PyPIibm-botocore—indirect
PyPIibm-cos-sdk-core2.16.2indirect
PyPImock1.3.0indirect
PyPInose1.3.7indirect
PyPIpsutil—indirect
PyPIpytest8.4.2indirect
PyPIpytest-cov6.3.0indirect
PyPIsetuptools80.9.0indirect
PyPItabulate0.7.7indirect
PyPIwheel0.45.1indirect
Dependency advisories 0

Installing pypi:ibm-cos-sdk-s3transfer@2.16.2 pulls in 9 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.