Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-15 11:29 UTC

code-payments / flipcash2-protobuf-api

Flipcash Protobuf API

Shell · Makefile · DockerfileMIT★ 1 star⑂ 1 forksince Nov 2025View on GitHub ↗

code-payments/flipcash2-protobuf-api holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Vitality (94/100) and lowest on Engineering Quality (17/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

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.

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

Ownership

Code PaymentsOrganization
44 followers33 public repossince Nov 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/code-payments/flipcash2-protobuf-apiv1.33.0-391 day ago

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
25.6/36Commit cadence — 37/52 weeks with commits
18/18Commit volume — 167 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year167
human_commit_share1
days_since_last_push1
active_weeks_last_year37

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 39 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~6.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count39
latest_release_tagv1.33.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases6.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?

24At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

54Moderate · 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
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
29.8/30PR acceptance — 166/167 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs166
open_issues0
closed_issues0
prs_merged_7d5
prs_decided_7d5
prs_merged_30d21
prs_decided_30d21
issue_closed_ratio—
closed_unmerged_prs1
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
30/30Ownership backing — organization-owned
0/20Verified domain
11.9/25Owner reach — 44 followers of code-payments
17.1/25Track record — 33 public repos, account ~2 yr old
Inputs used
followers44
owner_typeOrganization
is_verifiedno
owner_logincode-payments
public_repos33
account_age_days1,094

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 1 days ago
20/20Version history — 39 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/code-payments/flipcash2-protobuf-api
ecosystemsgo
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

17Critical · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
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_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
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?

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
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 — Found 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. 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.

46Weak · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.95
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes13,750
How it's scored
18/18One-command bootstrap — Makefile
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsno
lockfilesgo.sum
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Shell without a type-check config
0/55Manageable file sizes — no source files detected
Inputs used
primary_languageShell
largest_source_bytes—
source_files_sampled0
oversized_source_files0
Excluded from scoring (no data or not applicable): Manageable file sizes. Remaining weights renormalized.
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — proto/account/v1/flipcash_account_service.proto, proto/activity/v1/activity_feed_service.proto, proto/activity/v1/model.proto, proto/blob/v1/blob_storage_service.proto, proto/blob/v1/model.proto, proto/blocklist/v1/blocklist_service.proto, proto/blocklist/v1/model.proto, proto/chat/v1/chat_service.proto, proto/chat/v1/model.proto, proto/common/v1/common.proto, proto/community/v1/community_service.proto, proto/community/v1/model.proto, proto/contact/v1/contact_list_service.proto, proto/contact/v1/model.proto, proto/email/v1/email_verification_service.proto, proto/email/v1/model.proto, proto/event/v1/event_streaming_service.proto, proto/event/v1/model.proto, proto/iap/v1/iap_service.proto, proto/intent/v1/model.proto, proto/kyc/coinbase/v1/kyc_service.proto, proto/kyc/coinbase/v1/model.proto, proto/messaging/v1/messaging_service.proto, proto/messaging/v1/model.proto, proto/moderation/v1/model.proto, proto/moderation/v1/moderation_service.proto, proto/paymentrequest/v1/model.proto, proto/paymentrequest/v1/paymentrequest_service.proto, proto/phone/v1/model.proto, proto/phone/v1/phone_verification_service.proto, proto/poll/v1/model.proto, proto/poll/v1/poll_service.proto, proto/profile/v1/model.proto, proto/profile/v1/profile_service.proto, proto/push/v1/model.proto, proto/push/v1/push_service.proto, proto/reporting/v1/reporting_service.proto, proto/resolver/v1/model.proto, proto/resolver/v1/resolver_service.proto, proto/settings/v1/settings_service.proto, proto/thirdparty/v1/model.proto, proto/thirdparty/v1/third_party_service.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesproto/account/v1/flipcash_account_service.proto, proto/activity/v1/activity_feed_service.proto, proto/activity/v1/model.proto, proto/blob/v1/blob_storage_service.proto, proto/blob/v1/model.proto, proto/blocklist/v1/blocklist_service.proto, proto/blocklist/v1/model.proto, proto/chat/v1/chat_service.proto, proto/chat/v1/model.proto, proto/common/v1/common.proto, proto/community/v1/community_service.proto, proto/community/v1/model.proto, proto/contact/v1/contact_list_service.proto, proto/contact/v1/model.proto, proto/email/v1/email_verification_service.proto, proto/email/v1/model.proto, proto/event/v1/event_streaming_service.proto, proto/event/v1/model.proto, proto/iap/v1/iap_service.proto, proto/intent/v1/model.proto, proto/kyc/coinbase/v1/kyc_service.proto, proto/kyc/coinbase/v1/model.proto, proto/messaging/v1/messaging_service.proto, proto/messaging/v1/model.proto, proto/moderation/v1/model.proto, proto/moderation/v1/moderation_service.proto, proto/paymentrequest/v1/model.proto, proto/paymentrequest/v1/paymentrequest_service.proto, proto/phone/v1/model.proto, proto/phone/v1/phone_verification_service.proto, proto/poll/v1/model.proto, proto/poll/v1/poll_service.proto, proto/profile/v1/model.proto, proto/profile/v1/profile_service.proto, proto/push/v1/model.proto, proto/push/v1/push_service.proto, proto/reporting/v1/reporting_service.proto, proto/resolver/v1/model.proto, proto/resolver/v1/resolver_service.proto, proto/settings/v1/settings_service.proto, proto/thirdparty/v1/model.proto, proto/thirdparty/v1/third_party_service.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

1GitHub stars
1contributors
167commits, last 12 months
1days since last push
39releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2025-11-27: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 1 stars today.
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 1 ★ / 1 ⇿
1Stars
1Forks
35Releases

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.

Star history is shown as collected on 2025-11-27. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

0001111112025-112026-052026-10
Major 1Minor 33Patch 1
OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-11-15 11:29 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
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
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Gogithub.com/envoyproxy/protoc-gen-validatev1.2.1go.mod
Gogoogle.golang.org/grpcv1.71.1go.mod
Gogoogle.golang.org/protobufv1.36.6go.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.