Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-09 11:42 UTC

owncloud / coding-standard

📚Provides the ownCloud coding standard

PHPAGPL-3.0★ 4 stars⑂ 1 forksince Apr 2018View on GitHub ↗

owncloud/coding-standard holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (74/100) and lowest on Engineering Quality (21/100). It was last updated 23 days ago. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

1,340 followers181 public repossince Apr 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistowncloud/coding-standard5.3.24,42229153 days agocodestylestandardcodingowncloudphp-cs-fixer

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 23 days ago
4.2/36Commit cadence6/52 weeks with commits
9.4/18Commit volume10 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year10
human_commit_share0.978
days_since_last_push23
active_weeks_last_year6
How it's scored
27/27Ships releases29 releases published
27/36Release recencylatest release 153 days ago
19.8/27Release cadencea release every ~107.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count29
latest_release_tag5.3.2
releases_from_tagsno
days_since_latest_release153
mean_days_between_releases107.7
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?

48Weak · 17% of overall
How it's scored
7.7/60Stars4 stars
0/25Forks1 forks
7.1/15Watchers20 watchers
Inputs used
forks1
stars4
watchers20
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 (AGPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
48.6/80Monthly downloads4,422 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesowncloud/coding-standard
dependents0
ecosystemspackagist
total_downloads787,700
monthly_downloads4,422
unverified_packages_excluded

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.6/22.5Commit distributiontop contributor authored 75% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.753
How it's scored
42/42Issue resolution100% of issues closed
28.5/30PR acceptance39/41 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/12 approved changesets -- score normalized to 1
Inputs used
merged_prs39
open_issues0
closed_issues11
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
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
0/20Verified domainverified-domain status not read for this organization
22.5/25Owner reach1,340 followers of owncloud
25/25Track record181 public repos, account ~14 yr old
Inputs used
followers1,340
owner_typeOrganization
is_verified
owner_loginowncloud
public_repos181
account_age_days5,229
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 153 days ago
20/20Version history29 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesowncloud/coding-standard
ecosystemspackagist
any_deprecatedno
min_days_since_publish153

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
topicsowncloud, owncloud-classic, php
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?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/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
0.8/7.5Code-ReviewFound 2/12 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 17 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file 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_aggregate5.7
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.

39Weak · 4% of overall
How it's scored
45/45Agent instructionsagents.md
0/15Machine-readable docs (llms.txt)
30.2/40Legible commit history51 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.567
agent_instruction_filesagents.md
agent_instruction_max_bytes3,035
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 92
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
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/1 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes2,848
source_files_sampled1
oversized_source_files0

Key facts

4GitHub stars
5contributors
10commits, last 12 months
23days since last push
29releases
1bus factor
0open 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

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-08-09 11:42 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-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
1Code-ReviewFound 2/12 approved changesets -- score normalized to 1
10Contributorsproject has 17 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistfriendsofphp/php-cs-fixer^3.88.0composer.json
All dependencies 1

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

RegistryPackageVersionRelation
Packagistfriendsofphp/php-cs-fixerdirect
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.31.0 — full methodology · metrics wiki.

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