Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 14:31 UTC

greenbone / greenbone-feed-sync

Tool for downloading the Greenbone Community Feed

PythonGPL-3.0★ 31 stars⑂ 15 forkssince Dec 2022View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

greenbone/greenbone-feed-sync holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (46/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

GreenboneOrganization · verified domain
1,354 followers69 public repossince Sep 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIgreenbone-feed-sync25.4.2-2430 days ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
28.4/36Commit cadence — 41/52 weeks with commits
18/18Commit volume — 113 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year113
human_commit_share0.58
days_since_last_push0
active_weeks_last_year41

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 27 releases published
36/36Release recency — latest release 30 days ago
27/27Release cadence — a release every ~34.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count27
latest_release_tagv25.4.2
releases_from_tagsno
days_since_latest_release30
mean_days_between_releases34.8

Community & Adoption

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

46Weak · 17% of overall
How it's scored
24/60Stars — 31 stars
9.6/25Forks — 15 forks
3.3/15Watchers — 5 watchers
Inputs used
forks15
stars31
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.2/22.5Commit distribution — top contributor authored 64% of commits
13.5/13.5Contributor breadth — 14 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.637
How it's scored
36.8/42Issue resolution — 88% of issues closed
26.2/30PR acceptance — 325/372 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs325
open_issues1
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.875
closed_unmerged_prs47
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
22.5/25Owner reach — 1,354 followers of greenbone
25/25Track record — 69 public repos, account ~8 yr old
Inputs used
followers1,354
owner_typeOrganization
is_verifiedyes
owner_logingreenbone
public_repos69
account_age_days3,282

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 30 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgreenbone-feed-sync
ecosystemspypi
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
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://greenbone.github.io/docs/
10/10Repository description
10/10Topics — 9 topics
0/10Wiki
Inputs used
topicsfeed, greenbone, greenbone-community-edition, greenbone-vulnerability-management, openvas, openvas-scanner, base, python, tooling
has_wikino
homepagehttps://greenbone.github.io/docs/
docs_sitehttps://greenbone.github.io/docs/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

76Good · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
25/25Dependency lockfiles — uv.lock
20/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesuv.lock
manifestspyproject.toml
has_codeql_workflowyes
has_security_policyno
has_dependabot_configyes

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:greenbone-feed-sync@25.4.2 runtime dependency closure — what installing the published package pulls in — 5 packages. 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.1/40Legible commit history — 23 of 58 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.397
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 42 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.42
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/14 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes39,253
source_files_sampled14
oversized_source_files0

Key facts

31GitHub stars
14contributors
113commits, last 12 months
0days since last push
27releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'greenbone-feed-sync' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/greenbone/greenbone-feed-sync: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-10T14:31:07Z. Please include `D42C:21BF41:B765921:B2140D1:6AA2BF28` when reporting this issue.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
20Releases

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.

03581013151512023-022024-102026-06
Major 1Minor 10Patch 9

Each point covers 4 days.

Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPIrich>=13.2.0pyproject.toml
PyPItomli>=2.0.1pyproject.toml
PyPIshtab>=1.6.5pyproject.toml
All dependencies 37

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

RegistryPackageVersionRelation
PyPIrich15.0.0direct
PyPIshtab1.12.0direct
PyPItomli2.4.1direct
PyPIanyio4.13.0indirect
PyPIautohooks26.2.0indirect
PyPIautohooks-plugin-mypy23.10.0indirect
PyPIautohooks-plugin-ruff25.3.1indirect
PyPIcertifi2026.2.25indirect
PyPIcolorama0.4.6indirect
PyPIcolorful0.5.8indirect
PyPIcoverage7.13.5indirect
PyPIexceptiongroup1.3.1indirect
PyPIgit-cliff2.13.1indirect
PyPIgreenbone-feed-sync25.4.3.dev1indirect
PyPIh110.16.0indirect
PyPIh24.4.1indirect
PyPIhpack4.2.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIhyperframe6.1.0indirect
PyPIidna3.15indirect
PyPIlibrt0.8.1indirect
PyPIlxml6.1.0indirect
PyPImarkdown-it-py4.0.0indirect
PyPImdurl0.1.2indirect
PyPImypy1.20.0indirect
PyPImypy-extensions1.1.0indirect
PyPIpackaging26.3indirect
PyPIpathspec1.0.4indirect
PyPIpontos26.8.4indirect
PyPIpygments2.20.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIruff0.15.9indirect
PyPIsemver3.0.4indirect
PyPIsix1.17.0indirect
PyPItomlkit0.15.1indirect
PyPItyping-extensions4.15.0indirect
Dependency advisories 0

Installing pypi:greenbone-feed-sync@25.4.2 pulls in 5 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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.