Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 04:53 UTC

IBM / fp-go

Functional programming library for Go 1.24+, inspired by fp-ts. Uses generic type aliases for a clean, composable API. Provides Option, Either, Result, IO, IOResult, Reader, and ReaderIOResult monads, plus optics (Lens, Prism, Traversal) for immutable data manipulation. Supports Functor, Applicative, and Monad abstractions with do-notation-style

GoApache-2.0★ 2,019 stars⑂ 84 forkssince Jul 2023View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

IBM/fp-go holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (64/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

International Business MachinesOrganization · verified domain
8,677 followers3,945 public repossince Feb 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/IBM/fp-gov1.1.84-241265 days ago
Gogithub.com/IBM/fp-go/v2v2.3.132-2512 days ago

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 511 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_year511
human_commit_share0.71
days_since_last_push1
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~0.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.3.132
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases0.4
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?

64Moderate · 17% of overall
How it's scored
53.6/60Stars — 2,019 stars
16/25Forks — 84 forks
6.8/15Watchers — 18 watchers
Inputs used
forks84
stars2,019
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
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_servicescoveralls.io, pkg.go.dev
has_pull_request_templateno

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
13.5/13.5Contributor breadth — 16 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled16
top_contributor_share0.971
How it's scored
36.4/42Issue resolution — 87% of issues closed
29.4/30PR acceptance — 210/214 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_prs210
open_issues2
closed_issues13
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.867
closed_unmerged_prs4
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
25/25Owner reach — 8,677 followers of IBM
25/25Track record — 3,945 public repos, account ~14 yr old
Inputs used
followers8,677
owner_typeOrganization
is_verifiedyes
owner_loginIBM
public_repos3,945
account_age_days5,314

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on go
35/35Publish recency — latest publish 2 days ago
20/20Version history — 251 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/IBM/fp-go, github.com/IBM/fp-go/v2
ecosystemsgo
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/IBM/fp-go/tree/main/v2
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsfunctional-programming, go, golang, library, monad, utility
has_wikiyes
homepagehttps://github.com/IBM/fp-go/tree/main/v2
docs_sitehttps://github.com/IBM/fp-go/tree/main/v2
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 6 out of 6 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/30 approved changesets -- score normalized to 0
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
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
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 — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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
advisories2
affected_packages1
assessed_packages34
unassessed_packages0
affected_by_severityunknown 1
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 34 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.

86Excellent · 4% of overall
How it's scored
45/45Agent instructions — v2/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 62 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.873
agent_instruction_filesv2/AGENTS.md
agent_instruction_max_bytes11,626
How it's scored
12.6/18One-command bootstrap — gen/v2/go.mod, go.mod, v2/go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 29 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsgen/v2/go.mod, go.mod, v2/go.mod
dependency_bot_commit_share0.29
How it's scored
45/45Type-checkable code — Go (statically typed)
54.6/55Manageable file sizes — 19/2,599 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes193,847
source_files_sampled2,599
oversized_source_files19
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, samples
Inputs used
example_dirsexamples, samples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

2,019GitHub stars
16contributors
511commits, last 12 months
1days since last push
100releases
1bus factor
2open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 84 ⇿
0Stars
84Forks
94Releases

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.

0204060801008482023-082025-022026-09
Major 0Minor 0Patch 94

Each point covers 3 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-09-10 04:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests6 out of 6 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/30 approved changesets -- score normalized to 0
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
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Gogithub.com/stretchr/testifyv1.12.1go.mod
Gogithub.com/urfave/cli/v2v2.27.7go.mod
Gogithub.com/stretchr/testifyv1.12.1v2/go.mod
Gogithub.com/urfave/cli/v3v3.11.0v2/go.mod
All dependencies 34

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

RegistryPackageVersionRelation
Gogithub.com/stretchr/testifyv1.12.1direct
Gogithub.com/urfave/cli/v2v2.27.7direct
Gogithub.com/urfave/cli/v3v3.11.0direct
Gogithub.com/cpuguy83/go-md2man/v2v2.0.7indirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/dustin/go-humanizev1.0.1indirect
Gogithub.com/google/jsonschema-gov0.4.3indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/iancoleman/strcasev0.3.0indirect
Gogithub.com/ibm/fp-go/v2v2.3.132indirect
Gogithub.com/mattn/go-isattyv0.0.24indirect
Gogithub.com/modelcontextprotocol/go-sdkv1.7.0indirect
Gogithub.com/ncruces/go-strftimev1.0.0indirect
Gogithub.com/otiai10/copyv1.14.1indirect
Gogithub.com/otiai10/mintv1.6.3indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/remyoudompheng/bigfftv0.0.0-20230129092748-24d4a6f8daecindirect
Gogithub.com/russross/blackfriday/v2v2.1.0indirect
Gogithub.com/segmentio/asmv1.2.1indirect
Gogithub.com/segmentio/encodingv0.5.4indirect
Gogithub.com/xrash/smetricsv0.0.0-20240521201337-686a1a2994c1indirect
Gogithub.com/yosida95/uritemplate/v3v3.0.2indirect
Gogo.yaml.in/yaml/v3v3.0.5indirect
Gogolang.org/x/modv0.39.0indirect
Gogolang.org/x/oauth2v0.36.0indirect
Gogolang.org/x/syncv0.22.0indirect
Gogolang.org/x/sysv0.47.0indirect
Gogolang.org/x/timev0.15.0indirect
Gogolang.org/x/toolsv0.49.0indirect
Gogopkg.in/yaml.v3v3.0.1indirect
Gomodernc.org/libcv1.75.6indirect
Gomodernc.org/mathutilv1.7.1indirect
Gomodernc.org/memoryv1.12.1indirect
Gomodernc.org/sqlitev1.58.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/modv0.39.0indirectunknown21.27.0-rc.3

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