Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 15:35 UTC

burib / aws-region-table-parser

create a map of supported services per aws region

JavaScript · ShellMIT★ 19 stars⑂ 11 forkssince Apr 2016View on GitHub ↗

burib/aws-region-table-parser holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (95/100) and lowest on AI Readiness (17/100). It was last updated today. A single contributor accounts 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

buribPersonal account
0 followers104 public repossince Aug 2011

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmaws-region-table-parser2.0.71538456638 days agoawsamazonregion-table

Metrics by category

Vitality

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

95Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 655 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year655
human_commit_share1
days_since_last_push0
active_weeks_last_year52
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.0.506
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases1
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?

41Weak · 17% of overall
How it's scored
20.4/60Stars — 19 stars
8.3/25Forks — 11 forks
0/15Watchers — 1 watchers
Inputs used
forks11
stars19
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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
36.4/80Monthly downloads — 538 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesaws-region-table-parser
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads538
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10/22.5Commit distribution — top contributor authored 56% of commits
8.1/13.5Contributor breadth — 6 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.555
How it's scored
32.3/42Issue resolution — 77% of issues closed
30/30PR acceptance — 16/16 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs16
open_issues3
closed_issues10
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.769
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
0/25Owner reach — 0 followers of burib
25/25Track record — 104 public repos, account ~15 yr old
Inputs used
followers0
owner_typeUser
is_verified—
owner_loginburib
public_repos104
account_age_days5,557
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
14/35Publish recency — latest publish 638 days ago
20/20Version history — 456 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaws-region-table-parser
ecosystemsnpm
any_deprecatedno
min_days_since_publish638

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicsaws, aws-services, aws-regions
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?

47Weak · 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
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5SAST — no SAST tool detected
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
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, 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_packages62
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:aws-region-table-parser@2.0.71 runtime dependency closure — what installing the published package pulls in — 62 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.

17Critical · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0.5/40Legible commit history — 1 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.01
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/3 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes5,920
source_files_sampled3
oversized_source_files0

Key facts

19GitHub stars
6contributors
655commits, last 12 months
0days since last push
100releases
1bus factor
3open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
70Releases

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.

048121122017-032021-122026-09
Major 0Minor 0Patch 70

Each point covers 9 days.

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-10-20 15:35 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
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmjsdom26.0.0package.json
All dependencies 85

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

RegistryPackageVersionRelation
npmjsdom26.0.0direct
npm@asamuzakjp/css-color2.8.3indirect
npm@csstools/color-helpers5.0.1indirect
npm@csstools/css-calc2.1.1indirect
npm@csstools/css-color-parser3.0.7indirect
npm@csstools/css-parser-algorithms3.0.4indirect
npm@csstools/css-tokenizer3.0.3indirect
npmagent-base7.1.3indirect
npmajv6.12.6indirect
npmasn10.2.4indirect
npmassert-plus1.0.0indirect
npmasynckit0.4.0indirect
npmaws-sign20.7.0indirect
npmaws41.11.0indirect
npmbcrypt-pbkdf1.0.2indirect
npmcaseless0.12.0indirect
npmcombined-stream1.0.8indirect
npmcore-util-is1.0.2indirect
npmcssstyle4.2.1indirect
npmdashdash1.14.1indirect
npmdata-urls5.0.0indirect
npmdebug4.4.0indirect
npmdecimal.js10.4.3indirect
npmdelayed-stream1.0.0indirect
npmecc-jsbn0.1.2indirect
npmentities4.5.0indirect
npmextend3.0.2indirect
npmextsprintf1.3.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmforever-agent0.6.1indirect
npmform-data2.3.3indirect
npmform-data4.0.1indirect
npmgetpass0.1.7indirect
npmhar-schema2.0.0indirect
npmhar-validator5.1.5indirect
npmhtml-encoding-sniffer4.0.0indirect
npmhttp-proxy-agent7.0.2indirect
npmhttp-signature1.2.0indirect
npmhttps-proxy-agent7.0.6indirect
npmiconv-lite0.6.3indirect
npmis-potential-custom-element-name1.0.1indirect
npmis-typedarray1.0.0indirect
npmisstream0.1.2indirect
npmjsbn0.1.1indirect
npmjson-schema0.4.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stringify-safe5.0.1indirect
npmjsprim1.4.2indirect
npmlru-cache10.4.3indirect
npmmime-db1.49.0indirect
npmmime-types2.1.32indirect
npmms2.1.3indirect
npmnwsapi2.2.16indirect
npmoauth-sign0.9.0indirect
npmparse57.2.1indirect
npmperformance-now2.1.0indirect
npmpsl1.8.0indirect
npmpunycode2.3.1indirect
npmqs6.5.3indirect
npmrequest2.88.2indirect
npmrrweb-cssom0.8.0indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsaxes6.0.0indirect
npmsshpk1.16.1indirect
npmsymbol-tree3.2.4indirect
npmtldts6.1.72indirect
npmtldts-core6.1.72indirect
npmtough-cookie2.5.0indirect
npmtough-cookie5.1.0indirect
npmtr465.0.0indirect
npmtunnel-agent0.6.0indirect
npmtweetnacl0.14.5indirect
npmuri-js4.4.1indirect
npmuuid3.4.0indirect
npmverror1.10.0indirect
npmw3c-xmlserializer5.0.0indirect
npmwebidl-conversions7.0.0indirect
npmwhatwg-encoding3.1.1indirect
npmwhatwg-mimetype4.0.0indirect
npmwhatwg-url14.1.0indirect
npmws8.18.0indirect
npmxml-name-validator5.0.0indirect
npmxmlchars2.2.0indirect
Dependency advisories 0

Installing npm:aws-region-table-parser@2.0.71 pulls in 62 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.