Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-07 19:37 UTC

askama-rs / askama

A template rendering engine based on Jinja, generating type-safe Rust code at compile time.

RustApache-2.0★ 1,193 stars⑂ 65 forkssince Jun 2024View on GitHub ↗

askama-rs/askama holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on AI Readiness (63/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

AskamaOrganization
12 followers6 public repossince Jun 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioaskama0.16.13,722,162443 days agohtmljinja2markuptemplatetemplate-engine
crates.ioaskama_derive0.16.13,726,146483 days ago
crates.ioaskama_escape0.16.11,402,015183 days agoescapinghtmlno-std
crates.ioaskama_macros0.16.11,159,35193 days ago
crates.ioaskama_parser0.16.13,566,599163 days agohtmljinja2markuptemplatetemplate-engine

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
24.2/36Commit cadence35/52 weeks with commits
18/18Commit volume240 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year240
human_commit_share0.97
days_since_last_push0
active_weeks_last_year35
How it's scored
27/27Ships releases21 releases published
36/36Release recencylatest release 3 days ago
19.8/27Release cadencea release every ~55.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tagv0.16.1
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases55.4
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?

70Good · 17% of overall
How it's scored
49.9/60Stars1,193 stars
15.1/25Forks65 forks
3.9/15Watchers6 watchers
Inputs used
forks65
stars1,193
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads13,576,273 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesaskama, askama_derive, askama_escape, askama_macros, askama_parser
dependents
ecosystemscrates
total_downloads167,761,996
monthly_downloads13,576,273
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?

71Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.6/22.5Commit distributiontop contributor authored 30% of commits
13.5/13.5Contributor breadth98 contributors
10/10OpenSSF Scorecard: Contributorsproject has 44 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.305
How it's scored
38.4/42Issue resolution92% of issues closed
28.2/30PR acceptance498/530 decided PRs merged
6.5/13Newcomer PR acceptance2/4 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 4/13 approved changesets -- score normalized to 3
Inputs used
merged_prs498
open_issues17
closed_issues183
prs_merged_7d6
prs_decided_7d6
prs_merged_30d8
prs_decided_30d10
issue_closed_ratio0.915
closed_unmerged_prs32
first_time_authors_30d4
first_time_prs_merged_30d2
first_time_prs_decided_30d4
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
8/25Owner reach12 followers of askama-rs
10.6/25Track record6 public repos, account ~2 yr old
Inputs used
followers12
owner_typeOrganization
is_verifiedno
owner_loginaskama-rs
public_repos6
account_age_days812

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable5 package(s) on crates
35/35Publish recencylatest publish 3 days ago
20/20Version history48 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesaskama, askama_derive, askama_escape, askama_macros, askama_parser
ecosystemscrates
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.rustfmt.toml, clippy.toml, testing/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests11 out of 15 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://askama.rs
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicshtml, jinja, rust, template-engine
has_wikino
homepagehttps://askama.rs
docs_sitehttps://askama.rs
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.8/2.5CI-Tests11 out of 15 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 4/13 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 44 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
unassessed_packages45
affected_by_severitynone
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 4 resolved dependencies against OSV. 45 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.

63Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
23.6/40Legible commit history43 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.443
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, askama/Cargo.toml, askama_derive/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.rustfmt.toml, clippy.toml, testing/Cargo.toml ([lints])
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, askama/Cargo.toml, askama_derive/Cargo.toml, askama_escape/Cargo.toml, askama_macros/Cargo.toml, askama_parser/Cargo.toml, bench-build/Cargo.toml, examples/actix-web-app/Cargo.toml, examples/axum-app/Cargo.toml, examples/custom-escaper/Cargo.toml, examples/poem-app/Cargo.toml, examples/rocket-app/Cargo.toml, examples/warp-app/Cargo.toml, fuzzing/Cargo.toml, fuzzing/fuzz/Cargo.toml, testing-alloc/Cargo.toml, testing-no-std/Cargo.toml, testing-renamed/Cargo.toml, testing/Cargo.toml, testing/tests/clippy_lints/Cargo.toml, testing/tests/macro-include/a/Cargo.toml, testing/tests/macro-include/b/Cargo.toml, testing/tests/macro-include/c/Cargo.toml, testing/tests/print/Cargo.toml
dependency_bot_commit_share0.03
How it's scored
45/45Type-checkable codeRust (statically typed)
54.1/55Manageable file sizes4/240 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes77,741
source_files_sampled240
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,193GitHub stars
98contributors
240commits, last 12 months
0days since last push
21releases
2bus factor
17open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'askama_testing' from its registry
  • Could not fetch crates package 'bench-build' from its registry
  • Could not fetch crates package 'askama_testing-alloc' from its registry

More detail

Star and fork history 0 ★ / 65 ⇿
0Stars
65Forks
21Releases

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.

01325385063756532024-062025-072026-09
Major 0Minor 6Patch 13

Each point covers 3 days.

OpenSSF Scorecard 7.8 / 10
7.8aggregate

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-07 19:36 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
7CI-Tests11 out of 15 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 4/13 approved changesets -- score normalized to 3
10Contributorsproject has 44 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
crates.ioitoa1.0.11askama/Cargo.toml
crates.ioaskama_macros=0.16.1askama/Cargo.toml
crates.ioserde1.0askama/Cargo.toml
crates.ioserde_json1.0askama/Cargo.toml
crates.iopercent-encoding2.1.0askama/Cargo.toml
crates.ioparser=0.16.1askama_derive/Cargo.toml
crates.iobasic-toml0.1.1askama_derive/Cargo.toml
crates.ioglob0.3.3askama_derive/Cargo.toml
crates.iopulldown-cmark0.13.0askama_derive/Cargo.toml
crates.ioserde1.0askama_derive/Cargo.toml
crates.ioserde_derive1.0askama_derive/Cargo.toml
crates.iomemchr2askama_derive/Cargo.toml
crates.ioproc-macro21askama_derive/Cargo.toml
crates.ioquote1askama_derive/Cargo.toml
crates.iorustc-hash2.0.0askama_derive/Cargo.toml
crates.iosyn3.0.0askama_derive/Cargo.toml
crates.ioaskama_derive=0.16.1askama_macros/Cargo.toml
crates.iorustc-hash2.0.0askama_parser/Cargo.toml
crates.ioserde1.0askama_parser/Cargo.toml
crates.ioserde_derive1.0askama_parser/Cargo.toml
crates.iounicode-ident1.0.12askama_parser/Cargo.toml
crates.iowinnow1.0.0askama_parser/Cargo.toml
crates.ioaskamabench-build/Cargo.toml
crates.ioaskama_macrosbench-build/Cargo.toml
crates.ioaskamatesting/Cargo.toml
crates.ioserde_json1.0testing/Cargo.toml
crates.iocore1.0.0testing/Cargo.toml
All dependencies 49

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

RegistryPackageVersionRelation
crates.ioaskama_derive0.16.1direct
crates.ioaskama_macros0.16.1direct
crates.iobasic-tomldirect
crates.ioglobdirect
crates.ioitoadirect
crates.iomemchrdirect
crates.iopercent-encodingdirect
crates.ioproc-macro2direct
crates.iopulldown-cmarkdirect
crates.ioquotedirect
crates.iorustc-hashdirect
crates.ioserdedirect
crates.ioserde_derivedirect
crates.ioserde_jsondirect
crates.iosyndirect
crates.iounicode-identdirect
crates.iounicode-ident1.0.18direct
crates.iowinnowdirect
crates.ioactix-webindirect
crates.ioarbitraryindirect
crates.ioaskama_parser0.16.1indirect
crates.ioassert_matchesindirect
crates.ioaxumindirect
crates.ioconsoleindirect
crates.iocriterionindirect
crates.iodisplaydocindirect
crates.ioenv_loggerindirect
crates.iohtml-escapeindirect
crates.iohttpindirect
crates.iointentionally-emptyindirect
crates.iolibfuzzer-sysindirect
crates.iologindirect
crates.iopoemindirect
crates.iopretty-error-debugindirect
crates.ioprettypleaseindirect
crates.iorandindirect
crates.iorand_xoshiroindirect
crates.iorocketindirect
crates.iosimilarindirect
crates.iostrumindirect
crates.iothiserrorindirect
crates.iotokioindirect
crates.iotower-httpindirect
crates.iotracingindirect
crates.iotracing-subscriberindirect
crates.iotrybuildindirect
crates.iowarpindirect
PyPIjinja2indirect
PyPIpytestindirect
Dependency advisories 0

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

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 statisticscrates.io.