Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 10:40 UTC

benjamn / ast-types

Esprima-compatible implementation of the Mozilla JS Parser API

TypeScriptMIT★ 1,173 stars⑂ 194 forkssince Apr 2013View on GitHub ↗

benjamn/ast-types holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (75/100) and lowest on AI Readiness (50/100). It was last updated 6 days ago. A single contributor accounts 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

Ben NewmanPersonal account
2,926 followers166 public repossince Apr 2008Apollo Graph, Inc (formerly: Meteor, Facebook/Instagram, Quora, Mozilla)

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?

75Good · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
1.4/36Commit cadence — 2/52 weeks with commits
11.5/18Commit volume — 18 commits in the last year
10/10OpenSSF Scorecard: Maintained — 18 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year18
human_commit_share0.77
days_since_last_push6
active_weeks_last_year2

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 3 releases published
36/36Release recency — latest release 16 days ago
27/27Release cadence — a release every ~0 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv0.16.3
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases0
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?

73Good · 17% of overall
How it's scored
49.8/60Stars — 1,173 stars
19/25Forks — 194 forks
6.7/15Watchers — 17 watchers
Inputs used
forks194
stars1,173
watchers17
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 251,017,987 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesast-types
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads251,017,987
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.2/22.5Commit distribution — top contributor authored 72% of commits
13.5/13.5Contributor breadth — 62 contributors
10/10OpenSSF Scorecard: Contributors — project has 39 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled62
top_contributor_share0.725
How it's scored
19.9/42Issue resolution — 48% of issues closed
8.4/30PR acceptance — 212/753 decided PRs merged
4.3/13Newcomer PR acceptance — 1/3 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/16 approved changesets -- score normalized to 1
Inputs used
merged_prs212
open_issues93
closed_issues84
prs_merged_7d0
prs_decided_7d1
prs_merged_30d10
prs_decided_30d12
issue_closed_ratio0.475
closed_unmerged_prs541
first_time_authors_30d3
first_time_prs_merged_30d1
first_time_prs_decided_30d3
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
24.9/25Owner reach — 2,926 followers of benjamn
25/25Track record — 166 public repos, account ~18 yr old
Inputs used
followers2,926
owner_typeUser
is_verified—
owner_loginbenjamn
public_repos166
account_age_days6,735
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 16 days ago
20/20Version history — 175 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesast-types
ecosystemsnpm
any_deprecatedno
min_days_since_publish16

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 10 out of 18 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.2/2.5CI-Tests — 10 out of 18 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/16 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 39 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 18 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): 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_packages1
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:ast-types@0.16.3 runtime dependency closure — what installing the published package pulls in — 1 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
20.8/40Legible commit history — 30 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.39
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — script/consumer-typecheck/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 23 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsscript/consumer-typecheck/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.23
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
50.4/55Manageable file sizes — 4/48 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes268,381
source_files_sampled48
oversized_source_files4

Key facts

1,173GitHub stars
62contributors
18commits, last 12 months
6days since last push
3releases
1bus factor
93open 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 ★ / 194 ⇿
0Stars
194Forks

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.

0408012016020019042013-072019-112026-03

Each point covers 12 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-16 10:40 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests10 out of 18 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/16 approved changesets -- score normalized to 1
10Contributorsproject has 39 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmtslib^2.0.1package.json
All dependencies 154

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

RegistryPackageVersionRelation
npmtslib2.8.1direct
npm@babel/helper-string-parser7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@babel/parser7.29.8indirect
npm@babel/types7.20.5indirect
npm@babel/types7.29.8indirect
npm@cspotcode/source-map-support0.8.1indirect
npm@isaacs/cliui8.0.2indirect
npm@jridgewell/resolve-uri3.1.0indirect
npm@jridgewell/sourcemap-codec1.4.14indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@pkgjs/parseargs0.11.0indirect
npm@tsconfig/node101.0.9indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.3indirect
npm@types/esprima4.0.6indirect
npm@types/estree1.0.0indirect
npm@types/mocha10.0.10indirect
npm@types/node16.11.10indirect
npmacorn6.4.2indirect
npmacorn8.8.1indirect
npmacorn-dynamic-import4.0.0indirect
npmacorn-jsx5.3.2indirect
npmacorn-walk8.2.0indirect
npmansi-regex5.0.1indirect
npmansi-regex6.3.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmarg4.1.3indirect
npmargparse2.0.1indirect
npmassert2.0.0indirect
npmast-types0.16.1indirect
npmavailable-typed-arrays1.0.5indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion2.1.4indirect
npmbrace-expansion5.0.9indirect
npmbrowser-stdout1.3.1indirect
npmcall-bind1.0.2indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcreate-require1.1.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdefine-properties1.1.4indirect
npmdiff4.0.4indirect
npmdiff7.0.0indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmes6-object-assign1.1.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmeslint-visitor-keys3.3.0indirect
npmespree9.4.1indirect
npmesprima4.0.1indirect
npmesprima-fb15001.1001.0-dev-harmony-fbindirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmflow-parser0.195.2indirect
npmfor-each0.3.3indirect
npmforeground-child3.3.1indirect
npmfunction-bind1.1.1indirect
npmget-caller-file2.0.5indirect
npmget-intrinsic1.1.3indirect
npmglob10.4.4indirect
npmglob10.5.0indirect
npmglob13.0.6indirect
npmgopd1.0.1indirect
npmhas1.0.3indirect
npmhas-flag4.0.0indirect
npmhas-property-descriptors1.0.0indirect
npmhas-symbols1.0.3indirect
npmhas-tostringtag1.0.0indirect
npmhe1.2.0indirect
npminherits2.0.4indirect
npmis-arguments1.1.1indirect
npmis-callable1.2.7indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-generator-function1.0.10indirect
npmis-nan1.3.2indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-typed-array1.1.10indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjs-yaml4.3.2indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmlru-cache10.4.3indirect
npmlru-cache11.5.2indirect
npmmagic-string0.25.9indirect
npmmake-error1.3.6indirect
npmminimatch10.2.6indirect
npmminimatch9.0.9indirect
npmminipass7.1.3indirect
npmmocha11.8.0indirect
npmms2.1.3indirect
npmobject-is1.1.5indirect
npmobject-keys1.1.1indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpath-scurry2.0.2indirect
npmpicocolors1.1.1indirect
npmrandombytes2.1.0indirect
npmreaddirp4.1.2indirect
npmrecast0.23.1indirect
npmreify0.20.12indirect
npmrequire-directory2.1.1indirect
npmrimraf6.1.3indirect
npmsafe-buffer5.2.1indirect
npmsemver5.7.2indirect
npmserialize-javascript6.0.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmsource-map0.6.1indirect
npmsourcemap-codec1.4.8indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmto-fast-properties2.0.0indirect
npmts-node10.9.2indirect
npmtypescript4.4.4indirect
npmtypescript4.9.4indirect
npmtypescript5.9.3indirect
npmutil0.12.5indirect
npmv8-compile-cache-lib3.0.1indirect
npmwhich2.0.2indirect
npmwhich-typed-array1.1.9indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmy18n5.0.8indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyn3.1.1indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:ast-types@0.16.3 pulls in 1 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.