Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-12 22:06 UTC

aws / aws-sdk-js

AWS SDK for JavaScript v2 (End-of-Life as of 09/08/2025). The AWS SDK for JavaScript v3 in the browser and Node.js is available here: https://github.com/aws/aws-sdk-js-v3

JavaScript · RubyApache-2.0★ 7,604 stars⑂ 1,522 forkssince Sep 2012archivedView on GitHub ↗

aws/aws-sdk-js holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (96/100) and lowest on Vitality (31/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

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

Ownership

16,374 followers554 public repossince Aug 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmaws-sdk⚠ The AWS SDK for JavaScript (v2) has reached end-of-support, and no longer receives updates. Please migrate your code to use AWS SDK for JavaScript (v3). More info https://a.co/cUPnyil2.1693.037,698,4641,966246 days agoapiamazonawsec2simpledbs3sqssessnsroute53rdselasticachecloudfrontfpscloudformationcloudwatchdynamodbiamswfautoscalingcloudsearchelbloadbalancingemrmapreduceimportexportstoragegatewayworkflowebsvpcbeanstalkglacierkinesiscloudtrailwaf

Metrics by category

Vitality

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

31At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 246 days ago
1.4/36Commit cadence2/52 weeks with commits
5.4/18Commit volume3 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push246
active_weeks_last_year2
How it's scored
27/27Ships releases100 releases published
16.2/36Release recencylatest release 246 days ago
19.8/27Release cadencea release every ~52.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv2.1693.0
releases_from_tagsno
days_since_latest_release246
mean_days_between_releases52.1

Community & Adoption

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

96Exceptional · 17% of overall
How it's scored
60/60Stars7,604 stars
25/25Forks1,522 forks
13/15Watchers223 watchers
Inputs used
forks1,522
stars7,604
watchers223
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads37,698,464 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesaws-sdk
dependents
ecosystemsnpm
total_downloads
monthly_downloads37,698,464
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
13.5/22.5Commit distributiontop contributor authored 40% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 28 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.402
How it's scored
42/42Issue resolution100% of issues closed
22.8/30PR acceptance914/1,201 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 14/30 approved changesets -- score normalized to 4
Inputs used
merged_prs914
open_issues1
closed_issues3,259
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs287
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 backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach16,374 followers of aws
25/25Track record554 public repos, account ~13 yr old
Inputs used
followers16,374
owner_typeOrganization
is_verified
owner_loginaws
public_repos554
account_age_days5,097
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 246 days ago
20/20Version history1,966 published versions
0/20Not deprecatedaws-sdk: The AWS SDK for JavaScript (v2) has reached end-of-support, and no longer receives updates. Please migrate your code to use AWS SDK for JavaScript (v3). More info https://a.co/cUPnyil
Inputs used
packagesaws-sdk
ecosystemsnpm
any_deprecatedyes
min_days_since_publish246

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests3 out of 14 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://aws.amazon.com/developer/language/javascript/
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsaws-sdk, javascript, aws
has_wikino
homepagehttps://aws.amazon.com/developer/language/javascript/
docs_sitehttps://aws.amazon.com/developer/language/javascript/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0.5/2.5CI-Tests3 out of 14 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 14/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 28 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
0/7.5Maintainedproject is archived
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
1/5SASTSAST tool is not run on all commits -- score normalized to 2
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: uuid 8.0.0 (high 7.5)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
33.7/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 112 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages46
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:aws-sdk@2.1693.0 runtime dependency closure — what installing the published package pulls in — 46 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 instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16/40Legible commit history30 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.3
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 checkingts/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
How it's scored
27/45Type-checkable codeJavaScript with type-check config (ts/tsconfig.json)
44.5/55Manageable file sizes239/1,257 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes2,314,324
source_files_sampled1,257
oversized_source_files239
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 examplessample
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

7,604GitHub stars
99contributors
3commits, last 12 months
246days since last push
100releases
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 ★ / 1,522 ⇿
0Stars
1,522Forks
100Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

4006008001,0001,2001,4001,6001,52292017-102022-012026-05
Major 0Minor 100Patch 0

Each point covers 8 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-12 22:05 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests3 out of 14 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 14/30 approved changesets -- score normalized to 4
10Contributorsproject has 28 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
2SASTSAST tool is not run on all commits -- score normalized to 2
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
RubyGemsrakeGemfile
RubyGemsrdiscountGemfile
RubyGemsyard-sitemap~> 1.0Gemfile
RubyGemsyard-jsGemfile
RubyGemsyard~> 0.9.36Gemfile
RubyGemsparsejsGemfile
RubyGemsredcarpet~> 3.0Gemfile
RubyGemssamusGemfile
npmbuffer4.9.2package.json
npmevents1.1.1package.json
npmieee7541.1.13package.json
npmjmespath0.16.0package.json
npmquerystring0.2.0package.json
npmsax1.2.1package.json
npmurl0.10.3package.json
npmutil^0.12.4package.json
npmuuid8.0.0package.json
npmxml2js0.6.2package.json
All dependencies 33

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

RegistryPackageVersionRelation
npmbuffer4.9.2direct
npmevents1.1.1direct
npmieee7541.1.13direct
npmjmespath0.16.0direct
npmquerystring0.2.0direct
npmsax1.2.1direct
npmurl0.10.3direct
npmutil^0.12.4direct
npmuuid8.0.0direct
npmxml2js0.6.2direct
npm@types/node6.0.92indirect
npmbrowserify13.1.0indirect
npmchai^3.0indirect
npmcodecov^3.8.2indirect
npmcoffeeify*indirect
npmcoffeescript^1.12.7indirect
npmcucumber0.5.xindirect
npmeslint^5.8.0indirect
npmhash-test-vectors^1.3.2indirect
npminsert-module-globals^7.0.0indirect
npmistanbul*indirect
npmjasmine^2.5.3indirect
npmjasmine-core^2.5.2indirect
npmjson-loader^0.5.4indirect
npmkarma^4.1.0indirect
npmkarma-chrome-launcher2.2.0indirect
npmkarma-jasmine^1.1.0indirect
npmmocha^3.0.0indirect
npmrepl.history*indirect
npmsemver*indirect
npmtypescript2.0.8indirect
npmuglify-js2.xindirect
npmwebpack^1.15.0indirect
Dependency advisories 1

Installing npm:aws-sdk@2.1693.0 pulls in 46 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
uuid8.0.0directhigh113.0.1

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 statisticsnpm.