Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 02:18 UTC

PaulSchweizer / flowpipe

Very simple flow-based programming framework.

PythonMIT★ 275 stars⑂ 39 forkssince Apr 2017View on GitHub ↗

PaulSchweizer/flowpipe holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (96/100) and lowest on Vitality (44/100). It was last updated 151 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

Paul SchweizerPersonal account
69 followers33 public repossince Aug 2013

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
PyPIFlowpipe1.3.03,72526224 days ago

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 151 days ago
7.6/36Commit cadence — 11/52 weeks with commits
14.5/18Commit volume — 40 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year40
human_commit_share0.86
days_since_last_push151
active_weeks_last_year11
How it's scored
27/27Ships releases — 33 releases published
16.2/36Release recency — latest release 224 days ago
12.6/27Release cadence — a release every ~145.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count33
latest_release_tagv1.3.0
releases_from_tagsno
days_since_latest_release224
mean_days_between_releases145.3
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?

68Good · 17% of overall
How it's scored
39.5/60Stars — 275 stars
13.2/25Forks — 39 forks
4.7/15Watchers — 8 watchers
Inputs used
forks39
stars275
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesreadthedocs.org, shields.io
has_pull_request_templateno
How it's scored
47.6/80Monthly downloads — 3,725 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesFlowpipe
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,725
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5/22.5Commit distribution — top contributor authored 78% of commits
10.8/13.5Contributor breadth — 8 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.779
How it's scored
35.1/42Issue resolution — 84% of issues closed
26.4/30PR acceptance — 103/117 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 8/15 approved changesets -- score normalized to 5
Inputs used
merged_prs103
open_issues18
closed_issues91
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.835
closed_unmerged_prs14
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
13.3/25Owner reach — 69 followers of PaulSchweizer
23.2/25Track record — 33 public repos, account ~13 yr old
Inputs used
followers69
owner_typeUser
is_verified—
owner_loginPaulSchweizer
public_repos33
account_age_days4,771
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
26/35Publish recency — latest publish 224 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesFlowpipe
ecosystemspypi
any_deprecatedno
min_days_since_publish224

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .flake8, pyproject.toml ([tool.pylint], [tool.black], [tool.isort])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 19 out of 19 merged PRs checked by a CI test -- score normalized to 10
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 site — https://flowpipe.readthedocs.io/en/latest/
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicspython, flow-based-programming, graph, node, flow, hacktoberfest
has_wikiyes
homepage—
docs_sitehttps://flowpipe.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 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 — 19 out of 19 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
3.8/7.5Code-Review — Found 8/15 approved changesets -- score normalized to 5
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 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Packaging, 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
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_packages1
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:Flowpipe@1.3.0 runtime dependency closure — what installing the published package pulls in — 1 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.

62Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.7/40Legible commit history — 56 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.651
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — .flake8, pyproject.toml ([tool.pylint], [tool.black], [tool.isort])
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 13 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.13
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/29 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes29,440
source_files_sampled29
oversized_source_files0
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
Inputs used
example_dirsexamples
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

275GitHub stars
8contributors
40commits, last 12 months
151days since last push
33releases
1bus factor
18open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 39 ⇿
0Stars
39Forks
31Releases

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.

0102030403832018-072022-072026-08
Major 1Minor 11Patch 19

Each point covers 8 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-19 02:18 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests19 out of 19 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 8/15 approved changesets -- score normalized to 5
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
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIascii-canvas>=2.0.0pyproject.toml
All dependencies 45

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

RegistryPackageVersionRelation
PyPIascii-canvas—direct
PyPIascii-canvas2.0.1direct
PyPIastroid3.3.9indirect
PyPIblack25.9.0indirect
PyPIcfgv3.4.0indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.10.7indirect
PyPIcoverage7.13.4indirect
PyPIdill0.3.9indirect
PyPIdistlib0.3.9indirect
PyPIexceptiongroup1.2.2indirect
PyPIfilelock3.17.0indirect
PyPIfilelock3.20.3indirect
PyPIidentify2.6.9indirect
PyPIimportlib-metadata8.7.1indirect
PyPIiniconfig2.0.0indirect
PyPIisort6.1.0indirect
PyPIm2r2—indirect
PyPImccabe0.7.0indirect
PyPImock5.2.0indirect
PyPImypy1.15.0indirect
PyPImypy-extensions1.0.0indirect
PyPInodeenv1.9.1indirect
PyPInumpy2.0.2indirect
PyPInumpy2.2.6indirect
PyPInumpy2.4.2indirect
PyPIordereddict—indirect
PyPIpackaging24.2indirect
PyPIpathspec0.12.1indirect
PyPIplatformdirs4.3.6indirect
PyPIpluggy1.5.0indirect
PyPIpre-commit4.3.0indirect
PyPIpre-commit4.5.1indirect
PyPIpylint3.3.9indirect
PyPIpytest7.4.4indirect
PyPIpytest-cov7.0.0indirect
PyPIpytokens0.2.0indirect
PyPIpyyaml6.0.2indirect
PyPIsphinx—indirect
PyPItomli2.2.1indirect
PyPItomlkit0.13.2indirect
PyPItyping-extensions4.15.0indirect
PyPIvirtualenv20.36.1indirect
PyPIzipp3.23.0indirect
Dependency advisories 0

Installing pypi:Flowpipe@1.3.0 pulls in 1 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.