Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 14:37 UTC

inveniosoftware / invenio-celery

Integration layer between Celery and Invenio.

PythonMIT★ 0 stars⑂ 34 forkssince Sep 2015View on GitHub ↗

inveniosoftware/invenio-celery holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (86/100) and lowest on AI Readiness (33/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

198 followers170 public repossince Oct 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIinvenio-celery2.2.133,781280 days agoceleryinvenio

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.1/36Commit cadence3/52 weeks with commits
6.3/18Commit volume4 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year4
human_commit_share
days_since_last_push0
active_weeks_last_year3
How it's scored
16.2/27Ships releases21 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~192.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tagv2.2.1
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases192.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?

55Moderate · 17% of overall
How it's scored
0/60Stars0 stars
12.7/25Forks34 forks
10.6/15Watchers83 watchers
Inputs used
forks34
stars0
watchers83
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
6.3/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_templateyes
How it's scored
60.4/80Monthly downloads33,781 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesinvenio-celery
dependents
ecosystemspypi
total_downloads
monthly_downloads33,781
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?

86Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16/22.5Commit distributiontop contributor authored 29% of commits
13.5/13.5Contributor breadth22 contributors
10/10OpenSSF Scorecard: Contributorsproject has 23 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled22
top_contributor_share0.287
How it's scored
36.5/42Issue resolution87% of issues closed
27.2/30PR acceptance67/74 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 9/17 approved changesets -- score normalized to 5
Inputs used
merged_prs67
open_issues3
closed_issues20
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.87
closed_unmerged_prs7
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
16.5/25Owner reach198 followers of inveniosoftware
25/25Track record170 public repos, account ~14 yr old
Inputs used
followers198
owner_typeOrganization
is_verified
owner_logininveniosoftware
public_repos170
account_age_days5,375
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 0 days ago
20/20Version history28 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesinvenio-celery
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests5 out of 15 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://invenio-celery.readthedocs.io
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://invenio-celery.readthedocs.io
docs_sitehttps://invenio-celery.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.8/2.5CI-Tests5 out of 15 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 9/17 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 23 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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.

33At Risk · 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
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
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
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configno
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/11 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes9,909
source_files_sampled11
oversized_source_files0

Key facts

0GitHub stars
22contributors
4commits, last 12 months
0days since last push
21releases
3bus factor
3open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 4.3 / 10
4.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-16 14:37 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
3CI-Tests5 out of 15 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 9/17 approved changesets -- score normalized to 5
10Contributorsproject has 23 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
PyPIcelery>=5.1.0,<5.5pyproject.toml
PyPIflask-celeryext>=0.3.4pyproject.toml
PyPIinvenio-base>=2.3.0,<3.0.0pyproject.toml
PyPImsgpack>=0.6.2pyproject.toml
PyPIredis>=2.10.0pyproject.toml
All dependencies 8

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

RegistryPackageVersionRelation
PyPIcelerydirect
PyPIflask-celeryextdirect
PyPIinvenio-basedirect
PyPImsgpackdirect
PyPIredisdirect
PyPIpytest-black-ngindirect
PyPIpytest-invenioindirect
PyPIsphinxindirect
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.