Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 16:34 UTC

flownative / flow-google-cloudstorage

Flow resource adaptor for Google Cloud Storage

PHPMIT★ 2 stars⑂ 15 forkssince Nov 2015View on GitHub ↗

flownative/flow-google-cloudstorage holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (70/100) and lowest on Engineering Quality (21/100). It was last updated today. 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

FlownativeOrganization · verified domain
9 followers114 public repossince Dec 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistflownative/google-cloudstoragev6.2.04,977581 day ago

Metrics by category

Vitality

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

66Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
3.5/36Commit cadence5/52 weeks with commits
9.7/18Commit volume11 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year11
human_commit_share1
days_since_last_push0
active_weeks_last_year5
How it's scored
27/27Ships releases50 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~133.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count50
latest_release_tagv6.2.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases133.8
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?

35Weak · 17% of overall
How it's scored
0/60Stars2 stars
9.6/25Forks15 forks
2.7/15Watchers4 watchers
Inputs used
forks15
stars2
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
49.3/80Monthly downloads4,977 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesflownative/google-cloudstorage
dependents1
ecosystemspackagist
total_downloads199,949
monthly_downloads4,977
unverified_packages_excluded

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.3/22.5Commit distributiontop contributor authored 67% of commits
10.8/13.5Contributor breadth8 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.674
How it's scored
32/42Issue resolution76% of issues closed
28.3/30PR acceptance33/35 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 5/14 approved changesets -- score normalized to 3
Inputs used
merged_prs33
open_issues5
closed_issues16
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.762
closed_unmerged_prs2
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 backingorganization-owned
20/20Verified domain
7.2/25Owner reach9 followers of flownative
25/25Track record114 public repos, account ~11 yr old
Inputs used
followers9
owner_typeOrganization
is_verifiedyes
owner_loginflownative
public_repos114
account_age_days4,287

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 1 days ago
20/20Version history58 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesflownative/google-cloudstorage
ecosystemspackagist
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 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-Tests0 out of 14 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsneos-flow, google-cloud-storage, gcs
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?

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 14 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 5/14 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 7 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, 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.

23At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.2/40Legible commit history66 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.66
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/5 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes33,653
source_files_sampled5
oversized_source_files0

Key facts

2GitHub stars
8contributors
11commits, last 12 months
0days since last push
50releases
1bus factor
5open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
46Releases

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.

03581013151512016-032021-032026-02
Major 4Minor 10Patch 27

Each point covers 10 days.

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-18 16:33 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 14 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 5/14 approved changesets -- score normalized to 3
10Contributorsproject has 7 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistneos/flow^8.0 || ^9.0composer.json
Packagistgoogle/cloud-storage^1.40composer.json
All dependencies 6

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

RegistryPackageVersionRelation
Packagistgoogle/cloud-storagedirect
Packagistneos/flowdirect
Packagistext-jsonindirect
Packagistext-pdoindirect
Packagistext-zlibindirect
Packagistphpindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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