Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-15 17:22 UTC

dbrattli / Expression

Functional programming for Python

PythonMIT★ 766 stars⑂ 37 forkssince Sep 2020View on GitHub ↗

dbrattli/Expression holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (89/100) and lowest on Sustainability & Governance (54/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Dag BrattliPersonal account
273 followers47 public repossince Jun 2011@cognitedata

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIExpressionpoints to another repo — not scored5.7.011,352,643610 days ago

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
10/10OpenSSF Scorecard: Maintained12 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year0
human_commit_share0.98
days_since_last_push0
active_weeks_last_year0
How it's scored
27/27Ships releases77 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~105.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count77
latest_release_tagv5.7.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases105.2
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?

76Good · 17% of overall
How it's scored
46.8/60Stars766 stars
13/25Forks37 forks
8.1/15Watchers30 watchers
Inputs used
forks37
stars766
watchers30
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, readthedocs.org, shields.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 factor1 contributor(s) cover half of all commits
2.9/22.5Commit distributiontop contributor authored 87% of commits
13.5/13.5Contributor breadth17 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.873
How it's scored
40/42Issue resolution95% of issues closed
26.9/30PR acceptance181/202 decided PRs merged
4.3/13Newcomer PR acceptance1/3 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/28 approved changesets -- score normalized to 0
Inputs used
merged_prs181
open_issues3
closed_issues61
prs_merged_7d10
prs_decided_7d13
prs_merged_30d10
prs_decided_30d13
issue_closed_ratio0.953
closed_unmerged_prs21
first_time_authors_30d3
first_time_prs_merged_30d1
first_time_prs_decided_30d3
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.5/25Owner reach273 followers of dbrattli
24.2/25Track record47 public repos, account ~15 yr old
Inputs used
followers273
owner_typeUser
is_verified
owner_logindbrattli
public_repos47
account_age_days5,541
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests12 out of 28 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://expression.readthedocs.io
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsfunctional-programming, fsharp, python, railway-oriented-programming, oslash
has_wikiyes
homepagehttps://expression.readthedocs.io
docs_sitehttps://expression.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1/2.5CI-Tests12 out of 28 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/28 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained12 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
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_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages54
unassessed_packages14
affected_by_severitynone
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 54 resolved dependencies against OSV. 14 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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 instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
29.4/40Legible commit history54 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.551
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,044
How it's scored
18/18One-command bootstrapJustfile
22/22Automated tests
11/11Lint / format config
11/11Static type checkingexpression/py.typed, pyrightconfig.json
10/10Reproducible environmentdevcontainer, lockfile
10/10Demonstrated agent practice8 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesJustfile
has_devcontaineryes
has_linter_configyes
typecheck_configsexpression/py.typed, pyrightconfig.json
agent_commit_share0.08
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
27/45Type-checkable codePython with type-check config (expression/py.typed, pyrightconfig.json)
55/55Manageable file sizes0/89 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes30,983
source_files_sampled89
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesnotebooks
Inputs used
example_dirsnotebooks
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

766GitHub stars
17contributors
0commits, last 12 months
0days since last push
77releases
1bus factor
3open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi package 'Expression' points at a different repository (https://github.com/cognitedata/Expression); excluded from ecosystem scoring
  • deps.dev does not index pypi:Expression@5.7.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 37 ⇿
0Stars
37Forks
57Releases

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.

01325383722020-112023-082026-05
Major 4Minor 42Patch 11

Each point covers 6 days.

OpenSSF Scorecard 5.3 / 10
5.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-08-15 17:22 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
4CI-Tests12 out of 28 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/28 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
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 1
RegistryPackageVersion constraintManifest
PyPItyping-extensions>=4.6.0pyproject.toml
All dependencies 68

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

RegistryPackageVersionRelation
PyPItyping-extensions4.16.0direct
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIattrs26.1.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIcertifi2026.7.22indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.4indirect
PyPIcoveralls4.1.0indirect
PyPIdistlib0.4.3indirect
PyPIdunamai1.26.2indirect
PyPIexceptiongroup1.3.1indirect
PyPIfastjsonschema2.22.1indirect
PyPIfilelock3.32.3indirect
PyPIhypothesis6.165.9indirect
PyPIidentify2.6.19indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIjupyter-bookindirect
PyPIjupyter-core5.9.1indirect
PyPIjupytextindirect
PyPIjupytext1.19.5indirect
PyPIlinkify-it-pyindirect
PyPImarkdown-it-py4.2.0indirect
PyPImdit-py-plugins0.6.1indirect
PyPImdurl0.1.2indirect
PyPImyst-nbindirect
PyPInbformat5.11.0indirect
PyPInodeenv1.10.0indirect
PyPIpackaging26.3indirect
PyPIplatformdirs4.11.3indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.2indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpython-discovery1.5.2indirect
PyPIpyyaml6.0.3indirect
PyPIreferencing0.37.0indirect
PyPIrequests2.34.2indirect
PyPIrich15.0.0indirect
PyPIrpds-py0.30.0indirect
PyPIrpds-py2026.6.3indirect
PyPIruff0.16.3indirect
PyPIshellingham1.5.4indirect
PyPIsortedcontainers2.4.0indirect
PyPIsphinxindirect
PyPIsphinx-autodoc-typehintsindirect
PyPIsphinx-book-themeindirect
PyPIsphinx-commentsindirect
PyPIsphinx-copybuttonindirect
PyPIsphinx-external-tocindirect
PyPIsphinx-jupyterbook-latexindirect
PyPIsphinx-panelsindirect
PyPIsphinx-thebeindirect
PyPIsphinx-togglebuttonindirect
PyPItomli2.4.1indirect
PyPItraitlets5.16.1indirect
PyPItyper0.27.1indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib32.7.0indirect
PyPIvirtualenv21.7.4indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 54 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 14 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.