Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 00:44 UTC

timvink / mkdocs-git-revision-date-localized-plugin

MkDocs plugin to add a last updated date to your site pages

PythonMIT★ 268 stars⑂ 54 forkssince Nov 2019View on GitHub ↗
KindLibraryPluginhow this is determined

timvink/mkdocs-git-revision-date-localized-plugin holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (96/100) and lowest on AI Readiness (44/100). It was last updated 36 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Tim VinkPersonal account
70 followers27 public repossince Sep 2013

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPImkdocs-git-revision-date-localized-plugin1.5.3-5645 days agomkdocsplugin

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
18/36Push recencylast push 36 days ago
10.4/36Commit cadence15/52 weeks with commits
16.5/18Commit volume67 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year67
human_commit_share
days_since_last_push36
active_weeks_last_year15
How it's scored
27/27Ships releases58 releases published
36/36Release recencylatest release 45 days ago
19.8/27Release cadencea release every ~50.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count58
latest_release_tagv1.5.3
releases_from_tagsno
days_since_latest_release45
mean_days_between_releases50.3
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?

63Moderate · 17% of overall
How it's scored
39.4/60Stars268 stars
14.4/25Forks54 forks
1.7/15Watchers3 watchers
Inputs used
forks54
stars268
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.6/22.5Commit distributiontop contributor authored 75% of commits
13.5/13.5Contributor breadth40 contributors
10/10OpenSSF Scorecard: Contributorsproject has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled40
top_contributor_share0.753
How it's scored
42/42Issue resolution100% of issues closed
26.4/30PR acceptance87/99 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/12 approved changesets -- score normalized to 0
Inputs used
merged_prs87
open_issues0
closed_issues115
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs12
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
13.3/25Owner reach70 followers of timvink
22.5/25Track record27 public repos, account ~12 yr old
Inputs used
followers70
owner_typeUser
is_verified
owner_logintimvink
public_repos27
account_age_days4,673
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 45 days ago
20/20Version history56 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmkdocs-git-revision-date-localized-plugin
ecosystemspypi
any_deprecatedno
min_days_since_publish45

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.flake8
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://timvink.github.io/mkdocs-git-revision-date-localized-plugin/index.html
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsmkdocs, mkdocs-plugin, timeago, git, mkdocs-material
has_wikiyes
homepagehttps://timvink.github.io/mkdocs-git-revision-date-localized-plugin/index.html
docs_sitehttps://timvink.github.io/mkdocs-git-revision-date-localized-plugin/index.html
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/12 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 8 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

44Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.flake8
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/14 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes29,576
source_files_sampled14
oversized_source_files0
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 examplesnotebooks
Inputs used
example_dirsnotebooks
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

268GitHub stars
40contributors
67commits, last 12 months
36days since last push
58releases
1bus factor
0open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-07-17 00:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/12 approved changesets -- score normalized to 0
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIbabel>=2.7.0pyproject.toml
PyPIgitpython>=3.1.44pyproject.toml
PyPImkdocs>=1.0,<2pyproject.toml
PyPItzdata>=2023.3pyproject.toml
All dependencies 66

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

RegistryPackageVersionRelation
PyPIbabel2.17.0direct
PyPIgitpython3.1.50direct
PyPImkdocs1.6.1direct
PyPItzdata2025.2direct
PyPIbackrefs5.9indirect
PyPIcertifi2025.10.5indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.4indirect
PyPIclick8.2.1indirect
PyPIcodecov2.1.13indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.11.1indirect
PyPIdistlib0.4.0indirect
PyPIexceptiongroup1.3.0indirect
PyPIfilelock3.20.3indirect
PyPIghp-import2.1.0indirect
PyPIgitdb4.0.12indirect
PyPIidentify2.6.16indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown3.9indirect
PyPImarkdown-graphviz-inline1.1.3indirect
PyPImarkupsafe3.0.3indirect
PyPImdx-truly-sane-lists1.3indirect
PyPImergedeep1.3.4indirect
PyPImkdocs-gen-files0.5.0indirect
PyPImkdocs-get-deps0.2.0indirect
PyPImkdocs-git-authors-plugin0.10.0indirect
PyPImkdocs-material9.7.6indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImkdocs-monorepo-plugin1.1.2indirect
PyPImkdocs-redirects1.2.3indirect
PyPImkdocs-static-i18n1.3.0indirect
PyPImkdocs-techdocs-core1.6.2indirect
PyPInodeenv1.10.0indirect
PyPIpackaging25.0indirect
PyPIpaginate0.5.7indirect
PyPIpathspec0.12.1indirect
PyPIplantuml-markdown3.11.1indirect
PyPIplatformdirs4.5.0indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.5.1indirect
PyPIprek0.3.0indirect
PyPIproperdocs1.6.7indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions10.21.3indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov7.0.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-slugify8.0.4indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.33.0indirect
PyPIruff0.14.4indirect
PyPIsetuptoolsindirect
PyPIsetuptools-scmindirect
PyPIsix1.17.0indirect
PyPIsmmap5.0.2indirect
PyPItext-unidecode1.3indirect
PyPItomli2.3.0indirect
PyPIty0.0.13indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
PyPIvirtualenv20.36.1indirect
PyPIwatchdog6.0.0indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.