Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 10:16 UTC

phalcon / ide-stubs

Phalcon IDE Stubs

PHPCustom license★ 164 stars⑂ 54 forkssince Apr 2017View on GitHub ↗

phalcon/ide-stubs holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (88/100) and lowest on AI Readiness (35/100). It was last updated today. 2 contributors account for most of its recent work.

84
overall / 100
Excellent

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.

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

Ownership

202 followers64 public repossince Nov 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistphalcon/ide-stubsv5.16.065,1536524 days agostubautocompletestubsphalconidephpstormnetbeansdevtoolseclipse

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
4.8/36Commit cadence7/52 weeks with commits
13.3/18Commit volume29 commits in the last year
10/10OpenSSF Scorecard: Maintained25 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year29
human_commit_share
days_since_last_push0
active_weeks_last_year7
How it's scored
27/27Ships releases65 releases published
36/36Release recencylatest release 24 days ago
19.8/27Release cadencea release every ~52.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count65
latest_release_tagv5.16.0
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases52.1
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?

65Good · 17% of overall
How it's scored
35.9/60Stars164 stars
14.4/25Forks54 forks
6.7/15Watchers17 watchers
Inputs used
forks54
stars164
watchers17
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
64.2/80Monthly downloads65,153 downloads/month across packagist
14.4/20Registry dependents144 packages depend on it
Inputs used
packagesphalcon/ide-stubs
dependents144
ecosystemspackagist
total_downloads3,329,831
monthly_downloads65,153
unverified_packages_excluded

Sustainability & Governance

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

80Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15/22.5Commit distributiontop contributor authored 34% of commits
13.5/13.5Contributor breadth20 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled20
top_contributor_share0.335
How it's scored
39.7/42Issue resolution95% of issues closed
24.2/30PR acceptance71/88 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs71
open_issues2
closed_issues35
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.946
closed_unmerged_prs17
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
16.6/25Owner reach202 followers of phalcon
25/25Track record64 public repos, account ~14 yr old
Inputs used
followers202
owner_typeOrganization
is_verified
owner_loginphalcon
public_repos64
account_age_days5,347
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 24 days ago
20/20Version history65 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesphalcon/ide-stubs
ecosystemspackagist
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpcs.xml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests8 out of 10 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://phalcon.io
10/10Repository description
10/10Topics11 topics
0/10Wiki
Inputs used
topicsphalcon, devtools, ide, stubs, autocomplete, autocompletion, php, syntax-highlighting, ide-helper, phpstorm, phalcon-ide-stubs
has_wikino
homepagehttps://phalcon.io
docs_sitehttps://phalcon.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests8 out of 10 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/16 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 17 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained25 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpcs.xml
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes1/1,311 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes61,901
source_files_sampled1,311
oversized_source_files1

Key facts

164GitHub stars
20contributors
29commits, last 12 months
0days since last push
65releases
2bus factor
2open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-07-17 10:16 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-Tests8 out of 10 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/16 approved changesets -- score normalized to 0
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained25 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 51

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

RegistryPackageVersionRelation
Packagistamphp/amp3.1.1indirect
Packagistamphp/byte-stream2.1.2indirect
Packagistamphp/cache2.0.1indirect
Packagistamphp/dns2.4.0indirect
Packagistamphp/parallel2.4.0indirect
Packagistamphp/parser1.1.1indirect
Packagistamphp/pipeline1.2.4indirect
Packagistamphp/process2.1.0indirect
Packagistamphp/serialization1.1.0indirect
Packagistamphp/socket2.4.0indirect
Packagistamphp/sync2.3.0indirect
Packagistcomposer/pcre3.3.2indirect
Packagistcomposer/semver3.4.4indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistdanog/advanced-json-rpc3.2.3indirect
Packagistdaverandom/libdns2.1.0indirect
Packagistdnoegel/php-xdg-base-dir0.1.1indirect
Packagistdoctrine/deprecations1.1.6indirect
Packagistfelixfbecker/language-server-protocol1.5.3indirect
Packagistfidry/cpu-core-counter1.3.0indirect
Packagistkelunik/certificate1.1.3indirect
Packagistleague/uri7.8.1indirect
Packagistleague/uri-interfaces7.8.1indirect
Packagistnetresearch/jsonmapper5.0.1indirect
Packagistnikic/php-parser5.7.0indirect
Packagistpds/composer-script-names1.0.0indirect
Packagistpds/skeleton1.0.0indirect
Packagistphpdocumentor/reflection-common2.2.0indirect
Packagistphpdocumentor/reflection-docblock6.0.3indirect
Packagistphpdocumentor/type-resolver2.0.0indirect
Packagistphpstan/phpdoc-parser2.3.2indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/http-factory1.1.0indirect
Packagistpsr/http-message2.0indirect
Packagistpsr/log3.0.2indirect
Packagistrevolt/event-loop1.0.9indirect
Packagistsebastian/diff5.1.1indirect
Packagistspatie/array-to-xml3.4.4indirect
Packagistsquizlabs/php_codesniffer4.0.1indirect
Packagistsymfony/console6.4.41indirect
Packagistsymfony/deprecation-contracts3.7.0indirect
Packagistsymfony/filesystem6.4.39indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.38.1indirect
Packagistsymfony/polyfill-intl-normalizer1.38.0indirect
Packagistsymfony/polyfill-mbstring1.38.1indirect
Packagistsymfony/polyfill-php841.38.1indirect
Packagistsymfony/service-contracts3.7.0indirect
Packagistsymfony/string6.4.39indirect
Packagistvimeo/psalm6.16.1indirect
Packagistwebmozart/assert1.12.1indirect
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.11.0 — full methodology · metrics wiki.

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