Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 14:42 UTC

askama-rs / askama

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

RustApache-2.0★ 1,237 stars⑂ 69 forkssince Jun 2024View on GitHub ↗

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

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

92
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 78 is calibrated to 92 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.15,019,5534448 days agohtmljinja2markuptemplatetemplate-engine
crates.ioaskama_derive0.16.15,023,6124848 days ago—
crates.ioaskama_escape0.16.11,912,5721848 days agoescapinghtmlno-std
crates.ioaskama_macros0.16.11,787,890948 days ago—
crates.ioaskama_parser0.16.14,798,2421648 days agohtmljinja2markuptemplatetemplate-engine

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
22.8/36Commit cadence — 33/52 weeks with commits
18/18Commit volume — 230 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year230
human_commit_share0.98
days_since_last_push2
active_weeks_last_year33
How it's scored
27/27Ships releases — 21 releases published
36/36Release recency — latest release 48 days ago
19.8/27Release cadence — a release every ~55.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count21
latest_release_tagv0.16.1
releases_from_tagsno
days_since_latest_release48
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
50.2/60Stars — 1,237 stars
15.3/25Forks — 69 forks
3.9/15Watchers — 6 watchers
Inputs used
forks69
stars1,237
watchers6
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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 18,541,869 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesaskama, askama_derive, askama_escape, askama_macros, askama_parser
dependents—
ecosystemscrates
total_downloads200,498,431
monthly_downloads18,541,869
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?

73Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.7/22.5Commit distribution — top contributor authored 30% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 44 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.304
How it's scored
38.6/42Issue resolution — 92% of issues closed
28.2/30PR acceptance — 503/535 decided PRs merged
13/13Newcomer PR acceptance — 3/3 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 7/14 approved changesets -- score normalized to 5
Inputs used
merged_prs503
open_issues16
closed_issues185
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.92
closed_unmerged_prs32
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
8/25Owner reach — 12 followers of askama-rs
10.8/25Track record — 6 public repos, account ~2 yr old
Inputs used
followers12
owner_typeOrganization
is_verifiedno
owner_loginaskama-rs
public_repos6
account_age_days857

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 5 package(s) on crates
35/35Publish recency — latest publish 48 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaskama, askama_derive, askama_escape, askama_macros, askama_parser
ecosystemscrates
any_deprecatedno
min_days_since_publish48

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 1 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
18/20OpenSSF Scorecard: CI-Tests — 13 out of 14 merged PRs checked by a CI test -- score normalized to 9
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 site — https://askama.rs
10/10Repository description
10/10Topics — 4 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?

85Excellent · 16% of overall

Security posture

81Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 13 out of 14 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
3.8/7.5Code-Review — Found 7/14 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 44 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
7.5/7.5Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate8.1
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 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
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 instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
24.5/40Legible commit history — 45 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.459
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.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 checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 2 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_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.02
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.1/55Manageable file sizes — 4/241 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes77,741
source_files_sampled241
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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,237GitHub stars
98contributors
230commits, last 12 months
2days since last push
21releases
2bus factor
16open 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 ★ / 69 ⇿
0Stars
69Forks
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.

01325385063756932024-062025-082026-10
Major 0Minor 6Patch 13

Each point covers 3 days.

OpenSSF Scorecard 8.1 / 10
8.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-10-22 14:42 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
9CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 7/14 approved changesets -- score normalized to 5
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.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.iotoml1.0.7askama_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.ioaskama—bench-build/Cargo.toml
crates.ioaskama_macros—bench-build/Cargo.toml
crates.ioaskama—testing/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: 17 direct and 32 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.ioglob—direct
crates.ioitoa—direct
crates.iomemchr—direct
crates.iopercent-encoding—direct
crates.ioproc-macro2—direct
crates.iopulldown-cmark—direct
crates.ioquote—direct
crates.iorustc-hash—direct
crates.ioserde—direct
crates.ioserde_derive—direct
crates.ioserde_json—direct
crates.iosyn—direct
crates.iounicode-ident—direct
crates.iounicode-ident1.0.18direct
crates.iowinnow—direct
crates.ioactix-web—indirect
crates.ioarbitrary—indirect
crates.ioaskama_parser0.16.1indirect
crates.ioassert_matches—indirect
crates.ioaxum—indirect
crates.iobasic-toml—indirect
crates.ioconsole—indirect
crates.iocriterion—indirect
crates.iodisplaydoc—indirect
crates.ioenv_logger—indirect
crates.iohtml-escape—indirect
crates.iohttp—indirect
crates.iointentionally-empty—indirect
crates.iolibfuzzer-sys—indirect
crates.iolog—indirect
crates.iopoem—indirect
crates.iopretty-error-debug—indirect
crates.ioprettyplease—indirect
crates.iorand—indirect
crates.iorand_xoshiro—indirect
crates.iorocket—indirect
crates.iosimilar—indirect
crates.iostrum—indirect
crates.iothiserror—indirect
crates.iotokio—indirect
crates.iotower-http—indirect
crates.iotracing—indirect
crates.iotracing-subscriber—indirect
crates.iotrybuild—indirect
crates.iowarp—indirect
PyPIjinja2—indirect
PyPIpytest—indirect
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 statistics — crates.io.