Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-27 18:35 UTC

dgunning / edgartools

Read and analyze SEC EDGAR filings in Python. 10-K, 8-K, XBRL financials, Form 3/4/5, 13F, ADV — clean API, well-typed, MIT-licensed.

PythonMIT★ 2,516 stars⑂ 435 forkssince Dec 2022View on GitHub ↗

dgunning/edgartools holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Security (44/100). It was last updated today. A single contributor accounts for most of its recent work.

89
overall / 100
Excellent

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.

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

Ownership

Dwight GunningPersonal account
172 followers32 public repossince Mar 2012

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

Package ecosystems

Metrics by category

Vitality

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

96Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 0 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume2,003 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,003
human_commit_share1
days_since_last_push0
active_weeks_last_year52
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 7 days ago
27/27Release cadencea release every ~5.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv5.43.0
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases5.3

Community & Adoption

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

79Good · 17% of overall
How it's scored
55.2/60Stars2,516 stars
22/25Forks435 forks
8.4/15Watchers33 watchers
Inputs used
forks435
stars2,516
watchers33
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 93% of commits
13.5/13.5Contributor breadth51 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled51
top_contributor_share0.933
How it's scored
41.4/42Issue resolution98% of issues closed
24.2/30PR acceptance125/155 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs125
open_issues10
closed_issues636
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.985
closed_unmerged_prs30
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
16.1/25Owner reach172 followers of dgunning
23.1/25Track record32 public repos, account ~14 yr old
Inputs used
followers172
owner_typeUser
is_verified
owner_logindgunning
public_repos32
account_age_days5,252
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history426 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesedgartools
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://edgartools.readthedocs.io/
10/10Repository description
10/10Topics18 topics
10/10Wiki
Inputs used
topics10-k, 10-q, balance-sheet, edgar, filings, financials, insider-trading, sec, xbrl, 13-f, form-4, income-statement, cashflow-statement, company, cusip, tickers, bdc, 8-k
has_wikiyes
homepagehttps://edgartools.readthedocs.io/
docs_sitehttps://edgartools.readthedocs.io/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.8/2.5CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 8/30 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 9 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
7.5/7.5Maintained30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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.

79Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, edgar/entity/CLAUDE.md, edgar/xbrl/CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesCLAUDE.md, edgar/entity/CLAUDE.md, edgar/xbrl/CLAUDE.md
agent_instruction_max_bytes13,095
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config
11/11Static type checkingpyrightconfig.json
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice91 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspyrightconfig.json
agent_commit_share0.91
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (pyrightconfig.json)
54.4/55Manageable file sizes14/1,203 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes154,000
source_files_sampled1,203
oversized_source_files14
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
40/40Runnable examplesexamples, notebooks, samples
Inputs used
example_dirsexamples, notebooks, samples
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

2,516GitHub stars
51contributors
2,003commits, last 12 months
0days since last push
100releases
1bus factor
10open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:edgartools@5.43.1; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 435 ⇿
0Stars
435Forks
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.

010020030040050042992023-012024-102026-07
Major 1Minor 41Patch 58

Each point covers 4 days.

OpenSSF Scorecard 4.4 / 10
4.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-07-27 18:34 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
3CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
PyPIhttpx>=0.25.0pyproject.toml
PyPIpandas>=2.0.0pyproject.toml
PyPItabulate>=0.9.0pyproject.toml
PyPIpyarrow>=17.0.0pyproject.toml
PyPIbeautifulsoup4>=4.10.0pyproject.toml
PyPIlxml>=4.4pyproject.toml
PyPIrich>=13.8.0pyproject.toml
PyPIhumanize>=4.0.0pyproject.toml
PyPIstamina>=24.2.0pyproject.toml
PyPIorjson>=3.6.0pyproject.toml
PyPItextdistance>=4.5.0pyproject.toml
PyPIrank_bm25>=0.2.1pyproject.toml
PyPIrapidfuzz>=3.5.0pyproject.toml
PyPIunidecode>=1.2.0pyproject.toml
PyPIpydantic>=2.0.0pyproject.toml
PyPItqdm>=4.62.0pyproject.toml
PyPInest-asyncio>=1.5.1pyproject.toml
PyPIjinja2>=3.1.0pyproject.toml
PyPIpyrate-limiter>=3.0.0pyproject.toml
PyPIhttpxthrottlecache>=0.3.0,<0.5.0pyproject.toml
PyPItruststore>=0.9.0pyproject.toml
All dependencies 39

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

RegistryPackageVersionRelation
PyPIbeautifulsoup4direct
PyPIhttpxdirect
PyPIhttpxthrottlecachedirect
PyPIhumanizedirect
PyPIjinja2direct
PyPIlxmldirect
PyPInest-asynciodirect
PyPIorjsondirect
PyPIpandasdirect
PyPIpyarrowdirect
PyPIpydanticdirect
PyPIpyrate-limiterdirect
PyPIrank-bm25direct
PyPIrapidfuzzdirect
PyPIrichdirect
PyPIstaminadirect
PyPItabulatedirect
PyPItextdistancedirect
PyPItqdmdirect
PyPItruststoredirect
PyPIunidecodedirect
PyPIadlfsindirect
PyPIclickindirect
PyPIduckdbindirect
PyPIfsspecindirect
PyPIgcsfsindirect
PyPIhatchlingindirect
PyPImcpindirect
PyPImkdocsindirect
PyPImkdocs-materialindirect
PyPIpre-commitindirect
PyPIpytest-mockindirect
PyPIpytest-retryindirect
PyPIresponsesindirect
PyPIs3fsindirect
PyPIstarletteindirect
PyPItiktokenindirect
PyPIuvicornindirect
PyPIzstandardindirect
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.27.0 — full methodology · metrics wiki.

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