Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 21:51 UTC

phalcon / ide-stubs

Phalcon IDE Stubs

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

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

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

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

Ownership

The Phalcon PHP FrameworkOrganization · verified domain
204 followers69 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.20.367,3727213 days agostubautocompletestubsphalconidephpstormnetbeansdevtoolseclipse

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
28.8/36Push recency — last push 13 days ago
6.9/36Commit cadence — 10/52 weeks with commits
14.8/18Commit volume — 44 commits in the last year
10/10OpenSSF Scorecard: Maintained — 21 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year44
human_commit_share0.89
days_since_last_push13
active_weeks_last_year10

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 72 releases published
36/36Release recency — latest release 13 days ago
27/27Release cadence — a release every ~8.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count72
latest_release_tagv5.20.3
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases8.3
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/60Stars — 165 stars
14.4/25Forks — 54 forks
6.7/15Watchers — 17 watchers
Inputs used
forks54
stars165
watchers17
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license 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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, opencollective.com, shields.io
has_pull_request_templateno
How it's scored
64.4/80Monthly downloads — 67,372 downloads/month across packagist
14.4/20Registry dependents — 145 packages depend on it
Inputs used
packagesphalcon/ide-stubs
dependents145
ecosystemspackagist
total_downloads3,448,793
monthly_downloads67,372
unverified_packages_excluded—

Sustainability & Governance

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

81Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.4/22.5Commit distribution — top contributor authored 36% of commits
13.5/13.5Contributor breadth — 19 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled19
top_contributor_share0.362
How it's scored
39.7/42Issue resolution — 95% of issues closed
24.6/30PR acceptance — 78/95 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/19 approved changesets -- score normalized to 1
Inputs used
merged_prs78
open_issues2
closed_issues35
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.946
closed_unmerged_prs17
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
20/20Verified domain
16.6/25Owner reach — 204 followers of phalcon
25/25Track record — 69 public repos, account ~14 yr old
Inputs used
followers204
owner_typeOrganization
is_verifiedyes
owner_loginphalcon
public_repos69
account_age_days5,401

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 13 days ago
20/20Version history — 72 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesphalcon/ide-stubs
ecosystemspackagist
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 11 out of 12 merged PRs checked by a CI test -- score normalized to 9
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 site — https://phalcon.io
10/10Repository description
10/10Topics — 11 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?

62Moderate · 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/2.5CI-Tests — 11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/19 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 17 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 21 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages51
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 51 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

37Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21/40Legible commit history — 35 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.393
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpcs.xml
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 1/1,477 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes64,884
source_files_sampled1,477
oversized_source_files1

Key facts

165GitHub stars
19contributors
44commits, last 12 months
13days since last push
72releases
2bus factor
2open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 54 ⇿
0Stars
54Forks
55Releases

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.

01020304050605422017-082021-112026-02
Major 2Minor 12Patch 25

Each point covers 8 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-09 21:50 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
9CI-Tests11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/19 approved changesets -- score normalized to 1
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
10Maintained21 commit(s) and 5 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.3indirect
Packagistamphp/byte-stream2.1.2indirect
Packagistamphp/cache2.0.1indirect
Packagistamphp/dns2.4.1indirect
Packagistamphp/parallel2.4.0indirect
Packagistamphp/parser1.1.1indirect
Packagistamphp/pipeline1.2.7indirect
Packagistamphp/process2.1.0indirect
Packagistamphp/serialization1.1.0indirect
Packagistamphp/socket2.4.1indirect
Packagistamphp/sync2.3.0indirect
Packagistcomposer/pcre3.4.0indirect
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.8.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.3indirect
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.4indirect
Packagistsymfony/console6.4.44indirect
Packagistsymfony/deprecation-contracts3.7.1indirect
Packagistsymfony/filesystem6.4.44indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.41.0indirect
Packagistsymfony/polyfill-intl-normalizer1.42.0indirect
Packagistsymfony/polyfill-mbstring1.38.2indirect
Packagistsymfony/polyfill-php841.38.1indirect
Packagistsymfony/service-contracts3.7.1indirect
Packagistsymfony/string6.4.43indirect
Packagistvimeo/psalm6.16.1indirect
Packagistwebmozart/assert1.12.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 51 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.