Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 00:44 UTC

gristlabs / asttokens

Annotate Python AST trees with source text and token information

PythonApache-2.0★ 196 stars⑂ 47 forkssince Dec 2016View on GitHub ↗

gristlabs/asttokens holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on AI Readiness (47/100). It was last updated 61 days ago. 2 contributors account for most of its recent work.

73
overall / 100
Good

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.

73
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

Grist LabsOrganization
324 followers55 public repossince Jun 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIasttokens3.0.2-3661 days agocodeastparsetokenizerefactor

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
18/36Push recency — last push 61 days ago
3.5/36Commit cadence — 5/52 weeks with commits
8.1/18Commit volume — 7 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year7
human_commit_share0.86
days_since_last_push61
active_weeks_last_year5
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 61 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv3.0.2
releases_from_tagsno
days_since_latest_release61
mean_days_between_releases—
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?

53Moderate · 17% of overall
How it's scored
37.1/60Stars — 196 stars
13.9/25Forks — 47 forks
5/15Watchers — 9 watchers
Inputs used
forks47
stars196
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, readthedocs.org, shields.io
has_pull_request_templateno

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.5/22.5Commit distribution — top contributor authored 49% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled18
top_contributor_share0.49
How it's scored
33.2/42Issue resolution — 79% of issues closed
24.8/30PR acceptance — 91/110 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 12/19 approved changesets -- score normalized to 6
Inputs used
merged_prs91
open_issues13
closed_issues49
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.79
closed_unmerged_prs19
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 backing — organization-owned
0/20Verified domain
18.1/25Owner reach — 324 followers of gristlabs
24.7/25Track record — 55 public repos, account ~10 yr old
Inputs used
followers324
owner_typeOrganization
is_verifiedno
owner_logingristlabs
public_repos55
account_age_days3,739

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 61 days ago
20/20Version history — 36 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesasttokens
ecosystemspypi
any_deprecatedno
min_days_since_publish61

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 7 out of 26 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://asttokens.readthedocs.io/en/latest/index.html
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://asttokens.readthedocs.io/en/latest/index.html
has_readmeyes
has_docs_diryes
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.5/2.5CI-Tests — 7 out of 26 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 12/19 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 9 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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
2.2/7.5Vulnerabilities — 7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories14
affected_packages4
assessed_packages24
unassessed_packages2
affected_by_severityhigh 1, moderate 2, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 24 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
24.8/40Legible commit history — 40 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.465
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .pylintrc, tox.ini
11/11Static type checking — asttokens/py.typed
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 14 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_configsasttokens/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.14
How it's scored
27/45Type-checkable code — Python with type-check config (asttokens/py.typed)
52.6/55Manageable file sizes — 2/46 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes72,168
source_files_sampled46
oversized_source_files2

Key facts

196GitHub stars
18contributors
7commits, last 12 months
61days since last push
1releases
2bus factor
13open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'asttokens' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 47 ⇿
0Stars
47Forks
1Releases

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.

010203040504722018-022022-052026-09
Major 0Minor 0Patch 1

Each point covers 8 days.

OpenSSF Scorecard 5.1 / 10
5.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-09-12 00:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests7 out of 26 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 12/19 approved changesets -- score normalized to 6
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
All dependencies 26

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

RegistryPackageVersionRelation
PyPIalabaster0.7.13indirect
PyPIbabel2.12.1indirect
PyPIcertifi2024.7.4indirect
PyPIcharset-normalizer3.2.0indirect
PyPIdocutils0.18.1indirect
PyPIidna3.7indirect
PyPIimagesize1.4.1indirect
PyPIjinja23.1.6indirect
PyPImarkupsafe2.1.3indirect
PyPIpackaging23.1indirect
PyPIpygments2.16.1indirect
PyPIreadthedocs-sphinx-search0.3.2indirect
PyPIrequests2.32.4indirect
PyPIsetuptools—indirect
PyPIsetuptools-scm—indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsphinx6.2.1indirect
PyPIsphinx-rtd-theme1.2.2indirect
PyPIsphinxcontrib-applehelp1.0.4indirect
PyPIsphinxcontrib-devhelp1.0.2indirect
PyPIsphinxcontrib-htmlhelp2.0.1indirect
PyPIsphinxcontrib-jquery4.1indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.3indirect
PyPIsphinxcontrib-serializinghtml1.1.5indirect
PyPIurllib32.5.0indirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 24 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 0 are direct. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
urllib32.5.0indirecthigh82.7.0
idna3.7indirectmoderate23.15
requests2.32.4indirectmoderate22.33.0
pygments2.16.1indirectlow22.20.0

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 — PyPI.