Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 05:21 UTC

gajus / eslint-plugin-flowtype

Flow type linting rules for ESLint.

JavaScriptCustom license★ 1,069 stars⑂ 152 forkssince Feb 2016View on GitHub ↗

gajus/eslint-plugin-flowtype holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (76/100) and lowest on Vitality (25/100). It was last updated 895 days ago. A single contributor accounts for most of its recent work.

31
overall / 100
At Risk

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.

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

Ownership

Gajus KuizinasPersonal account
2,625 followers347 public repossince Aug 2011Contra

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
npmeslint-plugin-flowtype8.0.317,976,2371851749 days agoeslintpluginflowtype

Metrics by category

Vitality

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

25At Risk · 21% of overall
How it's scored
0/36Push recencylast push 895 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push895
active_weeks_last_year0
How it's scored
27/27Ships releases100 releases published
0/36Release recencylatest release 1,749 days ago
27/27Release cadencea release every ~4.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv8.0.3
releases_from_tagsno
days_since_latest_release1,749
mean_days_between_releases4.9
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?

76Good · 17% of overall
How it's scored
49.1/60Stars1,069 stars
18.2/25Forks152 forks
5/15Watchers9 watchers
Inputs used
forks152
stars1,069
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads17,976,237 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageseslint-plugin-flowtype
dependents
ecosystemsnpm
total_downloads
monthly_downloads17,976,237
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.3/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth70 contributors
10/10OpenSSF Scorecard: Contributorsproject has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled70
top_contributor_share0.543
How it's scored
37.2/42Issue resolution89% of issues closed
24.7/30PR acceptance177/215 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs177
open_issues35
closed_issues273
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.886
closed_unmerged_prs38
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
24.6/25Owner reach2,625 followers of gajus
25/25Track record347 public repos, account ~15 yr old
Inputs used
followers2,625
owner_typeUser
is_verified
owner_logingajus
public_repos347
account_age_days5,480
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 1,749 days ago
20/20Version history185 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageseslint-plugin-flowtype
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,749

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsflowtype, flow, eslint
has_wikino
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?

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 5/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 18 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): Branch-Protection, 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 advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
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:eslint-plugin-flowtype@8.0.3 runtime dependency closure — what installing the published package pulls in — 2 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.95
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-Dependenciesno 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
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/126 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes34,317
source_files_sampled126
oversized_source_files0

Key facts

1,069GitHub stars
70contributors
0commits, last 12 months
895days since last push
100releases
1bus factor
35open 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 ★ / 152 ⇿
0Stars
152Forks
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.

025507510012515014642016-032020-092025-02
Major 6Minor 36Patch 58

Each point covers 9 days.

OpenSSF Scorecard 3.3 / 10
3.3aggregate

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-13 05:21 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
0CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
10Contributorsproject has 18 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmlodash^4.17.21package.json
npmstring-natural-compare^3.0.1package.json
All dependencies 23

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

RegistryPackageVersionRelation
npmlodash^4.17.21direct
npmstring-natural-compare^3.0.1direct
npm@babel/cli^7.15.7indirect
npm@babel/core^7.15.8indirect
npm@babel/eslint-parser^7.15.8indirect
npm@babel/node^7.15.8indirect
npm@babel/plugin-proposal-object-rest-spread^7.15.6indirect
npm@babel/plugin-syntax-flow^7.16.0indirect
npm@babel/plugin-syntax-jsx^7.16.0indirect
npm@babel/preset-env^7.15.8indirect
npm@babel/register^7.15.3indirect
npmajv^8.6.3indirect
npmbabel-plugin-add-module-exports^1.0.4indirect
npmeslint^8.1.0indirect
npmeslint-config-canonical^32.15.0indirect
npmeslint-plugin-eslint-plugin^4.0.2indirect
npmgitdown^3.1.4indirect
npmglob^7.2.0indirect
npmhusky^7.0.4indirect
npmjsonlint^1.6.3indirect
npmmocha^9.1.3indirect
npmrimraf^3.0.2indirect
npmsemantic-release^18.0.0indirect
Dependency advisories 0

Installing npm:eslint-plugin-flowtype@8.0.3 pulls in 2 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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.