Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 18:48 UTC

ibexa / user

PHPCustom license★ 3 stars⑂ 3 forkssince Mar 2021View on GitHub ↗

ibexa/user holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (85/100) and lowest on AI Readiness (29/100). It was last updated today. 5 contributors account for most of its recent work.

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

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

Ownership

IbexaOrganization
40 followers98 public repossince May 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistibexa/userv5.0.929,73811019 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.1/36Commit cadence16/52 weeks with commits
13.5/18Commit volume31 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year31
human_commit_share
days_since_last_push0
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 19 days ago
27/27Release cadencea release every ~28.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv5.0.9
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases28.6
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?

47Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
2.5/25Forks3 forks
5.8/15Watchers12 watchers
Inputs used
forks3
stars3
watchers12
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
6.3/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_templateyes
How it's scored
59.6/80Monthly downloads29,738 downloads/month across packagist
7.6/20Registry dependents13 packages depend on it
Inputs used
packagesibexa/user
dependents13
ecosystemspackagist
total_downloads1,047,880
monthly_downloads29,738
unverified_packages_excluded

Sustainability & Governance

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

85Excellent · 23% of overall
How it's scored
45.9/54Bus factor5 contributor(s) cover half of all commits
18.7/22.5Commit distributiontop contributor authored 17% of commits
13.5/13.5Contributor breadth35 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled35
top_contributor_share0.169
How it's scored
0/42Issue resolutionno issues or no data
28.1/30PR acceptance118/126 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 11/29 approved changesets -- score normalized to 3
Inputs used
merged_prs118
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs8
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
11.6/25Owner reach40 followers of ibexa
25/25Track record98 public repos, account ~6 yr old
Inputs used
followers40
owner_typeOrganization
is_verified
owner_loginibexa
public_repos98
account_age_days2,254
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 19 days ago
20/20Version history110 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesibexa/user
ecosystemspackagist
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
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
0/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsibexa-bundle, ibexa-product
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests12 out of 12 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
2.2/7.5Code-ReviewFound 11/29 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 5 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.5Maintained13 commit(s) and 0 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
4/5SASTSAST tool is not run on all commits -- score normalized to 8
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): 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.

29At Risk · 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 config.php-cs-fixer.php, phpstan.neon
0/11Static type checking
0/10Reproducible environment
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
lockfiles
has_dockerfileno
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 sizes0/190 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes11,170
source_files_sampled190
oversized_source_files0

Key facts

3GitHub stars
35contributors
31commits, last 12 months
0days since last push
100releases
5bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-20 18:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 11/29 approved changesets -- score normalized to 3
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained13 commit(s) and 0 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
8SASTSAST tool is not run on all commits -- score normalized to 8
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
Packagistibexa/content-forms~6.0.x-devcomposer.json
Packagistibexa/core~6.0.x-devcomposer.json
Packagistibexa/notifications~6.0.x-devcomposer.json
Packagistjms/translation-bundle^2.4composer.json
Packagistsymfony/config^7.4composer.json
Packagistsymfony/dependency-injection^7.4composer.json
Packagistsymfony/event-dispatcher^7.4composer.json
Packagistsymfony/form^7.4composer.json
Packagistsymfony/http-foundation^7.4composer.json
Packagistsymfony/http-kernel^7.4composer.json
Packagistsymfony/intl^7.4composer.json
Packagistsymfony/options-resolver^7.4composer.json
Packagistsymfony/routing^7.4composer.json
Packagistsymfony/security-core^7.4composer.json
Packagistsymfony/security-http^7.4composer.json
Packagistsymfony/translation^7.4composer.json
Packagistsymfony/validator^7.4composer.json
Packagisttwig/twig^3.0composer.json
All dependencies 33

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

RegistryPackageVersionRelation
Packagistibexa/content-formsdirect
Packagistibexa/coredirect
Packagistibexa/notificationsdirect
Packagistjms/translation-bundledirect
Packagistsymfony/configdirect
Packagistsymfony/dependency-injectiondirect
Packagistsymfony/event-dispatcherdirect
Packagistsymfony/formdirect
Packagistsymfony/http-foundationdirect
Packagistsymfony/http-kerneldirect
Packagistsymfony/intldirect
Packagistsymfony/options-resolverdirect
Packagistsymfony/routingdirect
Packagistsymfony/security-coredirect
Packagistsymfony/security-httpdirect
Packagistsymfony/translationdirect
Packagistsymfony/validatordirect
Packagisttwig/twigdirect
Packagistibexa/code-styleindirect
Packagistibexa/design-engineindirect
Packagistibexa/doctrine-schemaindirect
Packagistibexa/fieldtype-richtextindirect
Packagistibexa/http-cacheindirect
Packagistibexa/rectorindirect
Packagistibexa/restindirect
Packagistibexa/searchindirect
Packagistmatthiasnoback/symfony-dependency-injection-testindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpstan/phpstan-symfonyindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/phpunit-bridgeindirect
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.16.0 — full methodology · metrics wiki.

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