Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 22:56 UTC

durandtibo / invoke-tasklib

Common, configurable Invoke tasks so every project doesn't reinvent tasks.py

Python · MakefileBSD-3-Clause★ 0 stars⑂ 0 forkssince Sep 2026View on GitHub ↗

durandtibo/invoke-tasklib holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (37/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Thibaut DurandPersonal account
110 followers77 public repossince Nov 2014Borealis AI

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
PyPIinvoke-tasklib0.0.850,94670 days agoautomationdevtoolsinvoketasks

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
1.4/36Commit cadence — 2/52 weeks with commits
16.5/18Commit volume — 68 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year68
human_commit_share0.812
days_since_last_push0
active_weeks_last_year2

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~2.1 days
8/10OpenSSF Scorecard: Signed-Releases — 4 out of the last 4 releases have a total of 4 signed artifacts.
Inputs used
releases_count7
latest_release_tagv0.0.8
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

37Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges15
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io, www.bestpractices.dev
has_pull_request_templateno
How it's scored
62.8/80Monthly downloads — 50,946 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesinvoke-tasklib
dependents—
ecosystemspypi
total_downloads—
monthly_downloads50,946
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 68/68 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_prs68
open_issues0
closed_issues0
prs_merged_7d10
prs_decided_7d10
prs_merged_30d47
prs_decided_30d47
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.7/25Owner reach — 110 followers of durandtibo
25/25Track record — 77 public repos, account ~11 yr old
Inputs used
followers110
owner_typeUser
is_verified—
owner_logindurandtibo
public_repos77
account_age_days4,332
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 pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 7 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesinvoke-tasklib
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 29 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.pylint], [tool.black])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://durandtibo.github.io/invoke-tasklib/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://durandtibo.github.io/invoke-tasklib/
docs_sitehttps://durandtibo.github.io/invoke-tasklib/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
4.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
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
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
1/5SAST — SAST tool is not run on all commits -- score normalized to 2
0/5Security-Policy — security policy file not detected
6/7.5Signed-Releases — 4 out of the last 4 releases have a total of 4 signed artifacts.
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_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.5

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_packages80
unassessed_packages0
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 80 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.

71Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 55 of 56 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.982
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — .make/Makefile, Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.pylint], [tool.black])
11/11Static type checking — src/invoke_tasklib/py.typed
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 69
8/8Automated maintenance — 7 of the last 69 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files.make/Makefile, Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/invoke_tasklib/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.101
How it's scored
27/45Type-checkable code — Python with type-check config (src/invoke_tasklib/py.typed)
55/55Manageable file sizes — 0/28 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes6,000
source_files_sampled28
oversized_source_files0

Key facts

0GitHub stars
1contributors
68commits, last 12 months
0days since last push
7releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • deps.dev does not index pypi:invoke-tasklib@0.0.8; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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-03 22:55 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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 0/19 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
2SASTSAST tool is not run on all commits -- score normalized to 2
0Security-Policysecurity policy file not detected
8Signed-Releases4 out of the last 4 releases have a total of 4 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIinvoke>=3.0pyproject.toml
All dependencies 80

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

RegistryPackageVersionRelation
PyPIinvoke3.0.3direct
PyPIbabel2.18.0indirect
PyPIbackrefs8.0indirect
PyPIboolean-py5.0indirect
PyPIcachecontrol0.14.4indirect
PyPIcertifi2026.7.22indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.1indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.1indirect
PyPIcyclonedx-python-lib11.12.0indirect
PyPIdefusedxml0.7.1indirect
PyPIdistlib0.4.3indirect
PyPIdocformatter1.7.8indirect
PyPIexceptiongroup1.3.1indirect
PyPIfeu0.8.3indirect
PyPIfilelock3.32.7indirect
PyPIghp-import2.1.0indirect
PyPIgitdb4.0.12indirect
PyPIgitpython3.1.62indirect
PyPIgriffelib2.3.0indirect
PyPIidentify2.6.19indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.0indirect
PyPIinvoke-tasklib0.0.8indirect
PyPIjinja23.1.6indirect
PyPIlicense-expression30.4.4indirect
PyPImarkdown3.10.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImike2.2.0indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.7indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImkdocstrings1.0.6indirect
PyPImkdocstrings-python2.0.8indirect
PyPImsgpack1.2.2indirect
PyPInodeenv1.10.0indirect
PyPIpackageurl-python0.17.6indirect
PyPIpackaging26.3indirect
PyPIpaginate0.5.7indirect
PyPIpathspec1.1.1indirect
PyPIpip26.2.1indirect
PyPIpip-api0.0.35indirect
PyPIpip-audit2.10.1indirect
PyPIpip-requirements-parser32.0.1indirect
PyPIplatformdirs4.11.11indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.2indirect
PyPIpy-serializable2.1.0indirect
PyPIpygments2.21.0indirect
PyPIpymdown-extensions12.0.1indirect
PyPIpyparsing3.3.3indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-timeout2.4.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.6.1indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.34.2indirect
PyPIrich15.0.0indirect
PyPIruff0.16.9indirect
PyPIsix1.17.0indirect
PyPIsmmap5.0.3indirect
PyPIsortedcontainers2.4.0indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPIty0.0.84indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.8.0indirect
PyPIverspec0.1.0indirect
PyPIvirtualenv21.9.0indirect
PyPIwatchdog6.0.0indirect
PyPIxdoctest1.3.2indirect
Dependency advisories 0

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

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 — PyPI.