Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 03:31 UTC

typst-community / setup-typst

📑 Install Typst and add it to the PATH with package management

TypeScriptMIT★ 181 stars⑂ 6 forkssince Apr 2023View on GitHub ↗

typst-community/setup-typst holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (79/100) and lowest on Security (54/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Typst CommunityOrganization · verified domain
150 followers34 public repossince Sep 2023

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

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
11.8/36Commit cadence — 17/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year30
human_commit_share0.789
days_since_last_push4
active_weeks_last_year17
How it's scored
27/27Ships releases — 20 releases published
36/36Release recency — latest release 16 days ago
19.8/27Release cadence — a release every ~60.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count20
latest_release_tagv5.3.0
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases60.5
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?

54Moderate · 17% of overall
How it's scored
36.6/60Stars — 181 stars
5.8/25Forks — 6 forks
1.7/15Watchers — 3 watchers
Inputs used
forks6
stars181
watchers3
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
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2/22.5Commit distribution — top contributor authored 91% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.909
How it's scored
42/42Issue resolution — 100% of issues closed
28/30PR acceptance — 57/61 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs57
open_issues0
closed_issues21
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs4
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
20/20Verified domain
15.7/25Owner reach — 150 followers of typst-community
17.4/25Track record — 34 public repos, account ~3 yr old
Inputs used
followers150
owner_typeOrganization
is_verifiedyes
owner_logintypst-community
public_repos34
account_age_days1,131

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 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
18/20OpenSSF Scorecard: CI-Tests — 25 out of 27 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/marketplace/actions/setup-typst
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsaction, compiler, installer, markup, typesetting, typst, github-actions
has_wikino
homepagehttps://github.com/marketplace/actions/setup-typst
docs_sitehttps://github.com/marketplace/actions/setup-typst
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 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
2.2/2.5CI-Tests — 25 out of 27 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/19 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 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 — 16 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
17.9/35Direct dependencies free of known advisories — 1 affected: fast-xml-parser 5.5.8 (moderate 6.1)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
34.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 179 days ago
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages70
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 70 resolved dependencies against OSV. 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32/40Legible commit history — 27 of 45 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.6
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 — tsconfig.json
10/10Reproducible environment — lockfile
7/10Demonstrated agent practice — 2 of the last 57 commits agent-authored or agent-credited
8/8Automated maintenance — 12 of the last 57 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.035
toolchain_manifests—
dependency_bot_commit_share0.211
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes9,974
source_files_sampled5
oversized_source_files0

Key facts

181GitHub stars
5contributors
30commits, last 12 months
4days since last push
20releases
1bus factor
0open 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 ★ / 6 ⇿
0Stars
6Forks
12Releases

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.

123456612023-072024-122026-06
Major 3Minor 5Patch 4

Each point covers 3 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-10-19 03:31 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests25 out of 27 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/19 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
npm@actions/cache^6.0.0package.json
npm@actions/core^3.0.0package.json
npm@actions/exec^3.0.0package.json
npm@actions/github^9.0.0package.json
npm@actions/tool-cache^4.0.0package.json
npm@openanime/hcl-unmarshal^1.0.6package.json
npm@types/hjson^2.4.6package.json
npm@types/ini^4.1.1package.json
npm@vercel/ncc^0.45.0package.json
npmfast-xml-parser^5.5.8package.json
npmhjson^3.2.2package.json
npmini^7.0.0package.json
npmsemver^7.8.5package.json
npmsmol-toml^1.9.0package.json
npmyaml^2.8.3package.json
All dependencies 70

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

RegistryPackageVersionRelation
npm@actions/cache6.0.0direct
npm@actions/core3.0.0direct
npm@actions/exec3.0.0direct
npm@actions/github9.0.0direct
npm@actions/tool-cache4.0.0direct
npm@openanime/hcl-unmarshal1.0.6direct
npm@types/hjson2.4.6direct
npm@types/ini4.1.1direct
npm@vercel/ncc0.45.0direct
npmfast-xml-parser5.5.8direct
npmhjson3.2.2direct
npmini7.0.0direct
npmsemver7.8.5direct
npmsmol-toml1.9.0direct
npmyaml2.8.3direct
npm@actions/glob0.6.1indirect
npm@actions/http-client3.0.2indirect
npm@actions/http-client4.0.0indirect
npm@actions/io3.0.2indirect
npm@azure/abort-controller2.1.2indirect
npm@azure/core-auth1.10.1indirect
npm@azure/core-client1.10.1indirect
npm@azure/core-http-compat2.3.2indirect
npm@azure/core-lro2.7.2indirect
npm@azure/core-paging1.6.2indirect
npm@azure/core-rest-pipeline1.23.0indirect
npm@azure/core-tracing1.3.1indirect
npm@azure/core-util1.13.1indirect
npm@azure/core-xml1.5.0indirect
npm@azure/logger1.3.0indirect
npm@azure/storage-blob12.31.0indirect
npm@azure/storage-common12.3.0indirect
npm@octokit/auth-token6.0.0indirect
npm@octokit/core7.0.6indirect
npm@octokit/endpoint11.0.3indirect
npm@octokit/graphql9.0.3indirect
npm@octokit/openapi-types27.0.0indirect
npm@octokit/plugin-paginate-rest14.0.0indirect
npm@octokit/plugin-rest-endpoint-methods17.0.0indirect
npm@octokit/request10.0.8indirect
npm@octokit/request-error7.1.0indirect
npm@octokit/types16.0.0indirect
npm@protobuf-ts/runtime2.11.1indirect
npm@protobuf-ts/runtime-rpc2.11.1indirect
npm@types/node24.12.0indirect
npm@types/semver7.7.1indirect
npm@typespec/ts-http-runtime0.3.4indirect
npmagent-base7.1.4indirect
npmbalanced-match1.0.2indirect
npmbefore-after-hook4.0.0indirect
npmbrace-expansion1.1.21indirect
npmconcat-map0.0.1indirect
npmdebug4.4.3indirect
npmevents3.3.0indirect
npmfast-content-type-parse3.0.0indirect
npmfast-xml-builder1.1.4indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmjson-with-bigint3.5.7indirect
npmminimatch3.1.5indirect
npmms2.1.3indirect
npmpath-expression-matcher1.2.0indirect
npmprettier3.4.2indirect
npmstrnum2.2.0indirect
npmtslib2.8.1indirect
npmtunnel0.0.6indirect
npmtypescript5.9.3indirect
npmundici6.29.0indirect
npmundici-types7.16.0indirect
npmuniversal-user-agent7.0.3indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 70 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
fast-xml-builder1.1.4indirecthigh11.1.7
fast-xml-parser5.5.8directmoderate15.7.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.