Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-14 06:41 UTC

postfinance / discovery

Service discovery for prometheus.

GoMIT★ 14 stars⑂ 1 forksince Sep 2020archivedView on GitHub ↗
KindApplicationLibraryhow this is determined

postfinance/discovery holds a health index of 16 out of 100, placing it in the Critical band. It scores highest on AI Readiness (66/100) and lowest on Vitality (19/100). The repository is archived, so no further maintenance is expected.

16
overall / 100
Critical

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.

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

Ownership

PostFinance AGOrganization · verified domain
53 followers44 public repossince Dec 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/postfinance/discoveryv0.9.0-281330 days ago

Metrics by category

Vitality

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

19Critical · 21% of overall
How it's scored
0/36Push recency — last push 848 days ago
0/36Commit cadence — 0/52 weeks with commits, discounted for automation: 23 of the last 100 commits human-authored, spanning 440 days
0/18Commit volume — 0 commits in the last year, discounted for automation: 23 of the last 100 commits human-authored, spanning 440 days
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year0
human_commit_share0.23
days_since_last_push848
active_weeks_last_year0
How it's scored
27/27Ships releases — 26 releases published
0/36Release recency — latest release 1,330 days ago
19.8/27Release cadence — a release every ~71.5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count26
latest_release_tagv0.9.0
releases_from_tagsno
days_since_latest_release1,330
mean_days_between_releases71.5

Community & Adoption

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

33At Risk · 17% of overall
How it's scored
18.1/60Stars — 14 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars14
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/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_templateno

Sustainability & Governance

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

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.1/22.5Commit distribution — top contributor authored 100% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.995
How it's scored
42/42Issue resolution — 100% of issues closed
22.3/30PR acceptance — 145/195 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_prs145
open_issues0
closed_issues23
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs50
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, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
12.5/25Owner reach — 53 followers of postfinance
24/25Track record — 44 public repos, account ~8 yr old
Inputs used
followers53
owner_typeOrganization
is_verifiedyes
owner_loginpostfinance
public_repos44
account_age_days3,231
How it's scored
25/25Published & resolvable — 1 package(s) on go
4/35Publish recency — latest publish 1,330 days ago
20/20Version history — 28 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/postfinance/discovery
ecosystemsgo
any_deprecatedno
min_days_since_publish1,330

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yaml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — no data
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 is archived
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 64 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): Branch-Protection, Code-Review, Packaging. 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.

66Good · 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 — 23 of 23 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .golangci.yaml
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 77 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
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0.77
How it's scored
45/45Type-checkable code — Go (statically typed)
53.6/55Manageable file sizes — 2/79 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes1,061,588
source_files_sampled79
oversized_source_files2
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — proto/google/api/annotations.proto, proto/google/api/http.proto, proto/postfinance/discovery/v1/namespace.proto, proto/postfinance/discovery/v1/namespace_api.proto, proto/postfinance/discovery/v1/server.proto, proto/postfinance/discovery/v1/server_api.proto, proto/postfinance/discovery/v1/service.proto, proto/postfinance/discovery/v1/service_api.proto, proto/postfinance/discovery/v1/targetgroup.proto, proto/postfinance/discovery/v1/token_api.proto, proto/postfinance/discovery/v1/tokeninfo.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesproto/google/api/annotations.proto, proto/google/api/http.proto, proto/postfinance/discovery/v1/namespace.proto, proto/postfinance/discovery/v1/namespace_api.proto, proto/postfinance/discovery/v1/server.proto, proto/postfinance/discovery/v1/server_api.proto, proto/postfinance/discovery/v1/service.proto, proto/postfinance/discovery/v1/service_api.proto, proto/postfinance/discovery/v1/targetgroup.proto, proto/postfinance/discovery/v1/token_api.proto, proto/postfinance/discovery/v1/tokeninfo.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

14GitHub stars
2contributors
0commits, last 12 months
848days since last push
26releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.3 / 10
3.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-10-14 06:41 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
0CI-Tests0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 30 changesets
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities64 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
Gogithub.com/alecthomas/kongv0.8.0go.mod
Gogithub.com/coreos/go-oidc/v3v3.9.0go.mod
Gogithub.com/golang-jwt/jwt/v4v4.5.0go.mod
Gogithub.com/golang/protobufv1.5.4go.mod
Gogithub.com/google/renameiov1.0.1go.mod
Gogithub.com/grpc-ecosystem/go-grpc-middlewarev1.4.0go.mod
Gogithub.com/grpc-ecosystem/go-grpc-prometheusv1.2.0go.mod
Gogithub.com/grpc-ecosystem/grpc-gateway/v2v2.19.1go.mod
Gogithub.com/pkg/errorsv0.9.1go.mod
Gogithub.com/postfinance/flashv0.5.1go.mod
Gogithub.com/postfinance/profilerv0.1.1go.mod
Gogithub.com/postfinance/singlev0.0.2go.mod
Gogithub.com/postfinance/storev0.3.2go.mod
Gogithub.com/prometheus/client_golangv1.18.0go.mod
Gogithub.com/satori/go.uuidv1.2.0go.mod
Gogithub.com/sethvargo/go-retryv0.2.4go.mod
Gogithub.com/stretchr/testifyv1.8.4go.mod
Gogithub.com/zbindenren/kingv0.3.2go.mod
Gogithub.com/zbindenren/sfmtv0.1.0go.mod
Gogo.uber.org/zapv1.26.0go.mod
Gogolang.org/x/oauth2v0.17.0go.mod
Gogolang.org/x/termv0.20.0go.mod
Gogoogle.golang.org/genproto/googleapis/apiv0.0.0-20240227224415-6ceb2ff114dego.mod
Gogoogle.golang.org/grpcv1.63.2go.mod
Gogoogle.golang.org/protobufv1.33.0go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
Gok8s.io/apimachineryv0.29.1go.mod
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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