Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-03 01:19 UTC

infocyph / PHPForge

Shared Composer-powered QA, refactoring, benchmark, release, hook and CI tooling for PHP projects.

PHPMIT★ 1 star⑂ 0 forkssince Apr 2026View on GitHub ↗
KindPluginCommand-line toolLibraryhow this is determined

infocyph/PHPForge holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (64/100) and lowest on Vitality (43/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

InfocyphOrganization
2 followers31 public repossince Apr 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistinfocyph/phpforge1.022,56413 days agotestingqualitybenchmarkrefactoringcomposer-pluginstatic-analysisinfocyph

Metrics by category

Vitality

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

43Weak · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
6.9/36Commit cadence10/52 weeks with commits
18/18Commit volume386 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year386
human_commit_share1
days_since_last_push0
active_weeks_last_year10
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

46Weak · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
45.5/80Monthly downloads2,564 downloads/month across packagist
8.9/20Registry dependents21 packages depend on it
Inputs used
packagesinfocyph/phpforge
dependents21
ecosystemspackagist
total_downloads5,023
monthly_downloads2,564
unverified_packages_excluded

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
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance113/113 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs113
open_issues0
closed_issues0
prs_merged_7d7
prs_decided_7d7
prs_merged_30d21
prs_decided_30d21
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
3.4/25Owner reach2 followers of infocyph
15.6/25Track record31 public repos, account ~2 yr old
Inputs used
followers2
owner_typeOrganization
is_verified
owner_logininfocyph
public_repos31
account_age_days847
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 3 days ago
4/20Version history1 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesinfocyph/phpforge
ecosystemspackagist
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
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?

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/10 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
5/5SASTSAST tool is run on all commits
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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate6.2
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.

46Weak · 4% of overall
How it's scored
45/45Agent instructionsresources/AGENTS.md
0/15Machine-readable docs (llms.txt)
17.6/40Legible commit history33 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.33
agent_instruction_filesresources/AGENTS.md
agent_instruction_max_bytes6,778
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
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/61 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes41,550
source_files_sampled61
oversized_source_files0

Key facts

1GitHub stars
1contributors
386commits, last 12 months
0days since last push
0releases
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 6.2 / 10
6.2aggregate

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-03 01:19 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
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/10 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
Packagistcaptainhook/captainhook^5.29.2composer.json
Packagistdeptrac/deptrac^4.7.1composer.json
Packagistergebnis/composer-normalize^2.52composer.json
Packagistinfocyph/phpprobe^0.4.4composer.json
Packagistlaravel/pint^1.30.0composer.json
Packagistpestphp/pest>=3.0 <5.0composer.json
Packagistpestphp/pest-plugin-drift>=3.0 <5.0composer.json
Packagistrector/rector^2.5.8composer.json
Packagistsquizlabs/php_codesniffer^4.0.1composer.json
Packagistsymfony/console>=7.4.9 <9.0composer.json
Packagistsymfony/process>=7.4.8 <9.0composer.json
Packagistsymfony/var-dumper>=7.4.8 <9.0composer.json
Packagistsymfony/yaml>=7.4 <9.0composer.json
Packagisttomasvotruba/cognitive-complexity^1.0composer.json
Packagistvimeo/psalm^6.16.1composer.json
All dependencies 21

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

RegistryPackageVersionRelation
Packagistcaptainhook/captainhookdirect
Packagistdeptrac/deptracdirect
Packagistergebnis/composer-normalizedirect
Packagistinfocyph/phpprobedirect
Packagistlaravel/pintdirect
Packagistpestphp/pestdirect
Packagistpestphp/pest-plugin-driftdirect
Packagistrector/rectordirect
Packagistsquizlabs/php_codesnifferdirect
Packagistsymfony/consoledirect
Packagistsymfony/processdirect
Packagistsymfony/var-dumperdirect
Packagistsymfony/yamldirect
Packagisttomasvotruba/cognitive-complexitydirect
Packagistvimeo/psalmdirect
Packagistcomposer-plugin-apiindirect
Packagistcomposer/composerindirect
Packagistphpindirect
Packagistphpbench/phpbenchindirect
Packagistphpdocumentor/type-resolverindirect
Packagistphpstan/phpstanindirect
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.30.0 — full methodology · metrics wiki.

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