Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 22:00 UTC

airbnb / javascript

JavaScript Style Guide

JavaScriptMIT★ 148,093 stars⑂ 26,610 forkssince Nov 2012View on GitHub ↗

airbnb/javascript holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (79/100) and lowest on Vitality (9/100). It was last updated 110 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

AirbnbOrganization
5,673 followers203 public repossince Mar 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmairbnb-style2.0.08,83524107 days agostyle-guidelintairbnbes6es2015reactjsx

Metrics by category

Vitality

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

9Critical · 21% of overall
How it's scored
9.9/36Push recencylast push 110 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
1/10OpenSSF Scorecard: Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year1
human_commit_share1
days_since_last_push110
active_weeks_last_year1
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

79Good · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars148,093 stars
25/25Forks26,610 forks
15/15Watchers3,658 watchers
Inputs used
forks26,610
stars148,093
watchers3,658
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
52.6/80Monthly downloads8,835 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesairbnb-style
dependents
ecosystemsnpm
total_downloads
monthly_downloads8,835
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?

73Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.9/22.5Commit distributiontop contributor authored 47% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 65 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.471
How it's scored
39/42Issue resolution93% of issues closed
14.9/30PR acceptance822/1,650 decided PRs merged
0/13Newcomer PR acceptance0/10 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs822
open_issues100
closed_issues1,315
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d10
issue_closed_ratio0.929
closed_unmerged_prs828
first_time_authors_30d8
first_time_prs_merged_30d0
first_time_prs_decided_30d10
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach5,673 followers of airbnb
25/25Track record203 public repos, account ~15 yr old
Inputs used
followers5,673
owner_typeOrganization
is_verified
owner_loginairbnb
public_repos203
account_age_days5,606
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 4,107 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesairbnb-style
ecosystemsnpm
any_deprecatedno
min_days_since_publish4,107

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests10 out of 20 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics14 topics
10/10Wiki
Inputs used
topicsjavascript, eslint, naming-conventions, arrow-functions, style-guide, style-linter, es6, es2015, linting, styleguide, es2016, es2017, es2018, tc39
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?

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.2/2.5CI-Tests10 out of 20 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 65 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

27At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
5.9/40Legible commit history11 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.11
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc
0/11Static type checking
0/10Reproducible environment
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
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 codeJavaScript without a type-check config
55/55Manageable file sizes0/28 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes28,295
source_files_sampled28
oversized_source_files0

Key facts

148,093GitHub stars
100contributors
1commits, last 12 months
110days since last push
0releases
2bus factor
100open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 26,610 ⇿
0Stars
26,610Forks

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.

25,50025,75026,00026,25026,50026,75026,610132024-112025-092026-08

Each point covers 2 days.

OpenSSF Scorecard 6.1 / 10
6.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-04 21:59 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
5CI-Tests10 out of 20 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 65 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
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
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 19

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

RegistryPackageVersionRelation
npm@babel/runtime^7.25.6indirect
npmbabel-preset-airbnb^4.5.0indirect
npmbabel-tape-runner^3.0.0indirect
npmconfusing-browser-globals^1.0.11indirect
npmeclint^2.8.1indirect
npmeslint^7.32.0 || ^8.2.0indirect
npmeslint-config-airbnb-base^15.0.0indirect
npmeslint-find-rules^4.1.0indirect
npmeslint-plugin-import^2.30.0indirect
npmeslint-plugin-jsx-a11y^6.10.0indirect
npmeslint-plugin-react^7.36.1indirect
npmeslint-plugin-react-hooks^5.1.0indirect
npmin-publish^2.0.1indirect
npmmarkdownlint^0.29.0indirect
npmmarkdownlint-cli^0.35.0indirect
npmreact>= 0.13.0indirect
npmrimraf^6.0.1indirect
npmsafe-publish-latest^2.0.0indirect
npmtape^5.9.0indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.