Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 22:44 UTC

IBM / ibm-cos-sdk-js

ibm-cos-sdk-js

JavaScript · RubyApache-2.0★ 39 stars⑂ 20 forkssince Sep 2017View on GitHub ↗

IBM/ibm-cos-sdk-js holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (76/100) and lowest on Vitality (41/100). It was last updated 95 days ago. 2 contributors account for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

International Business MachinesOrganization · verified domain
9,061 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 publishTags
npmibm-cos-sdk1.15.286,7655095 days agoapis3iam

Metrics by category

Vitality

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

41Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 95 days ago
2.8/36Commit cadence — 4/52 weeks with commits
6.3/18Commit volume — 4 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year4
human_commit_share0.99
days_since_last_push95
active_weeks_last_year4
How it's scored
27/27Ships releases — 49 releases published
27/36Release recency — latest release 95 days ago
12.6/27Release cadence — a release every ~136 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count49
latest_release_tag1.15.2
releases_from_tagsno
days_since_latest_release95
mean_days_between_releases136
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?

55Moderate · 17% of overall
How it's scored
25.6/60Stars — 39 stars
10.7/25Forks — 20 forks
6/15Watchers — 13 watchers
Inputs used
forks20
stars39
watchers13
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
65.8/80Monthly downloads — 86,765 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesibm-cos-sdk
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads86,765
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12/22.5Commit distribution — top contributor authored 47% of commits
13.5/13.5Contributor breadth — 89 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled89
top_contributor_share0.467
How it's scored
41.5/42Issue resolution — 99% of issues closed
1.6/30PR acceptance — 1/19 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues1
closed_issues89
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.989
closed_unmerged_prs18
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,061 followers of IBM
25/25Track record — 2,732 public repos, account ~14 yr old
Inputs used
followers9,061
owner_typeOrganization
is_verifiedyes
owner_loginIBM
public_repos2,732
account_age_days5,387

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 95 days ago
20/20Version history — 50 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesibm-cos-sdk
ecosystemsnpm
any_deprecatedno
min_days_since_publish95

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 — .eslintrc
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
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?

49Weak · 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
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 17 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages51
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 npm:ibm-cos-sdk@1.15.2 runtime dependency closure — what installing the published package pulls in — 51 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)
4.8/40Legible commit history — 9 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.091
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc
11/11Static type checking — ts/tsconfig.json
10/10Reproducible environment — lockfile
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
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsts/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
27/45Type-checkable code — JavaScript with type-check config (ts/tsconfig.json)
53.5/55Manageable file sizes — 7/264 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes570,548
source_files_sampled264
oversized_source_files7
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 — sample
Inputs used
example_dirssample
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

39GitHub stars
89contributors
4commits, last 12 months
95days since last push
49releases
2bus factor
1open issues
npm, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 20 ⇿
0Stars
20Forks
48Releases

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.

0481216201932017-092022-022026-07
Major 1Minor 15Patch 32

Each point covers 9 days.

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-11-21 22:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
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 17 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
RubyGemsrake—Gemfile
RubyGemsrdiscount—Gemfile
RubyGemsyard-sitemap~> 1.0Gemfile
RubyGemsyard-js—Gemfile
RubyGemsyard~> 0.9.42Gemfile
RubyGemsparsejs—Gemfile
RubyGemsredcarpet~> 3.0Gemfile
RubyGemssamus—Gemfile
npmbuffer^4.9.2package.json
npmjmespath^0.16.0package.json
npmurl^0.11.4package.json
npmutil^0.12.5package.json
npmuuid^14.0.1package.json
npmxml2js^0.6.2package.json
npmxmlbuilder^10.1.1package.json
All dependencies 33

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

RegistryPackageVersionRelation
npmbuffer^4.9.2direct
npmjmespath^0.16.0direct
npmurl^0.11.4direct
npmutil^0.12.5direct
npmuuid^14.0.1direct
npmxml2js^0.6.2direct
npmxmlbuilder^10.1.1direct
RubyGemsparsejs—direct
RubyGemsrake13.0.6direct
RubyGemsrdiscount2.2.7.4direct
RubyGemsredcarpet—direct
RubyGemsredcarpet3.5.1direct
RubyGemssamus3.0.9direct
RubyGemsyard—direct
RubyGemsyard0.9.42direct
RubyGemsyard-sitemap1.0.1direct
npm@cucumber/cucumber^11.3.0indirect
npm@types/node^6.14.13indirect
npmbrowserify^16.5.2indirect
npmchai^3.5.0indirect
npmcodecov^3.8.3indirect
npmcoffeescript^1.12.7indirect
npmcoveralls^3.1.1indirect
npmeslint^5.16.0indirect
npminsert-module-globals^7.2.1indirect
npmistanbul*indirect
npmkarma^6.4.4indirect
npmkarma-jasmine^1.1.2indirect
npmmocha^5.2.0indirect
npmtypescript^3.9.10indirect
npmuglify-js^3.19.3indirect
RubyGemskpeg1.1.0indirect
RubyGemspry—indirect
Dependency advisories 0

Installing npm:ibm-cos-sdk@1.15.2 pulls in 51 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 — npm.