Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-15 16:17 UTC

digitalcz / openid-connect

PHP implementation of https://openid.net/specs/openid-connect-core-1_0.html

PHPMIT★ 7 stars⑂ 1 forksince Dec 2021View on GitHub ↗

digitalcz/openid-connect holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (69/100) and lowest on Community & Adoption (45/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

DigitalCzOrganization
3 followers8 public repossince Jun 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistdigitalcz/openid-connectv1.4.05,28217105 days agosymfonyphpopenidopenid-connectoidc

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
11.9/18Commit volume — 20 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year20
human_commit_share0.819
days_since_last_push0
active_weeks_last_year8
How it's scored
27/27Ships releases — 14 releases published
27/36Release recency — latest release 104 days ago
19.8/27Release cadence — a release every ~84.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv1.4.0
releases_from_tagsno
days_since_latest_release104
mean_days_between_releases84.9
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?

45Weak · 17% of overall
How it's scored
12.6/60Stars — 7 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars7
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, poser.pugx.org
has_pull_request_templateyes
How it's scored
49.6/80Monthly downloads — 5,282 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packagesdigitalcz/openid-connect
dependents0
ecosystemspackagist
total_downloads33,990
monthly_downloads5,282
unverified_packages_excluded—

Sustainability & Governance

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

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.973
How it's scored
24.5/42Issue resolution — 58% of issues closed
22/30PR acceptance — 60/82 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/18 approved changesets -- score normalized to 1
Inputs used
merged_prs60
open_issues5
closed_issues7
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.583
closed_unmerged_prs22
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
0/20Verified domain
4.3/25Owner reach — 3 followers of digitalcz
18.9/25Track record — 8 public repos, account ~10 yr old
Inputs used
followers3
owner_typeOrganization
is_verifiedno
owner_logindigitalcz
public_repos8
account_age_days3,781

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 105 days ago
20/20Version history — 17 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdigitalcz/openid-connect
ecosystemspackagist
any_deprecatedno
min_days_since_publish105

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 24 out of 27 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
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?

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2/2.5CI-Tests — 24 out of 27 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/18 approved changesets -- score normalized to 1
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
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 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
29.8/40Legible commit history — 43 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.558
agent_instruction_files.github/copilot-instructions.md, CLAUDE.md
agent_instruction_max_bytes6,259
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpcs.xml, phpstan.neon
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 26 of the last 94 commits agent-authored or agent-credited
8/8Automated maintenance — 17 of the last 94 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.277
toolchain_manifests—
dependency_bot_commit_share0.181
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/108 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes32,312
source_files_sampled108
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

7GitHub stars
2contributors
20commits, last 12 months
0days since last push
14releases
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

OpenSSF Scorecard 4.7 / 10
4.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-10-15 16:17 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
8CI-Tests24 out of 27 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/18 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 3
RegistryPackageVersion constraintManifest
Packagistsymfony/cache-contracts^3.6composer.json
Packagistsymfony/http-client-contracts^3.6composer.json
Packagistweb-token/jwt-library^4.0composer.json
All dependencies 13

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

RegistryPackageVersionRelation
Packagistsymfony/cache-contracts—direct
Packagistsymfony/http-client-contracts—direct
Packagistweb-token/jwt-library—direct
Packagistdigitalcz/coding-standard—indirect
Packagistergebnis/composer-normalize—indirect
Packagistphp—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistsymfony/cache—indirect
Packagistsymfony/http-client—indirect
Packagistsymfony/var-dumper—indirect
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 statistics — Packagist.