Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 01:16 UTC

yiisoft / user

Convenient user identity management and access checking.

PHPBSD-3-Clause★ 23 stars⑂ 7 forkssince Oct 2020View on GitHub ↗

yiisoft/user holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (85/100) and lowest on Security (32/100). It was last updated 7 days ago. 2 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

34
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 64 is calibrated to 73 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Yii SoftwareOrganization · verified domain
689 followers214 public repossince Aug 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistyiisoft/user2.3.211,2998262 days agouseryiisoft

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
6.2/36Commit cadence — 9/52 weeks with commits
11.1/18Commit volume — 16 commits in the last year
10/10OpenSSF Scorecard: Maintained — 12 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year16
human_commit_share0.94
days_since_last_push7
active_weeks_last_year9
How it's scored
27/27Ships releases — 7 releases published
16.2/36Release recency — latest release 262 days ago
12.6/27Release cadence — a release every ~214.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tag2.3.2
releases_from_tagsno
days_since_latest_release262
mean_days_between_releases214.5
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?

62Moderate · 17% of overall
How it's scored
21.8/60Stars — 23 stars
6.5/25Forks — 7 forks
5.6/15Watchers — 11 watchers
Inputs used
forks7
stars23
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
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_badges12
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, poser.pugx.org, shields.io
has_pull_request_templateyes
How it's scored
54/80Monthly downloads — 11,299 downloads/month across packagist
10.3/20Registry dependents — 34 packages depend on it
Inputs used
packagesyiisoft/user
dependents34
ecosystemspackagist
total_downloads165,896
monthly_downloads11,299
unverified_packages_excluded—

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.3/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 14 contributors
10/10OpenSSF Scorecard: Contributors — project has 37 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled14
top_contributor_share0.32
How it's scored
34.5/42Issue resolution — 82% of issues closed
20.8/30PR acceptance — 72/104 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 8/29 approved changesets -- score normalized to 2
Inputs used
merged_prs72
open_issues5
closed_issues23
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.821
closed_unmerged_prs32
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
20.4/25Owner reach — 689 followers of yiisoft
25/25Track record — 214 public repos, account ~15 yr old
Inputs used
followers689
owner_typeOrganization
is_verifiedyes
owner_loginyiisoft
public_repos214
account_age_days5,501
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
26/35Publish recency — latest publish 262 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesyiisoft/user
ecosystemspackagist
any_deprecatedno
min_days_since_publish262

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.dist.php
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 14 out of 22 merged PRs checked by a CI test -- score normalized to 6
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://www.yiiframework.com/
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsyii3, user, identity, hacktoberfest, login, logout, remember-me
has_wikino
homepagehttps://www.yiiframework.com/
docs_sitehttps://www.yiiframework.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

32At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.5/2.5CI-Tests — 14 out of 22 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 8/29 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 37 contributing companies or organizations
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
7.5/7.5Maintained — 12 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
2.5/5SAST — SAST tool is not run on all commits -- score normalized to 5
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_aggregate6.5
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier32
security_posture_before_jurisdiction65
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30.1/40Legible commit history — 53 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.564
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 6 of the last 100 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
toolchain_manifests—
dependency_bot_commit_share0.06
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/40 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes19,208
source_files_sampled40
oversized_source_files0

Key facts

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

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
4Releases

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.

123456612020-112022-102024-10
Major 1Minor 2Patch 1

Each point covers 4 days.

OpenSSF Scorecard 6.5 / 10
6.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-09-12 01:15 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
6CI-Tests14 out of 22 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/29 approved changesets -- score normalized to 2
10Contributorsproject has 37 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
5SASTSAST tool is not run on all commits -- score normalized to 5
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Packagistpsr/event-dispatcher^1.0composer.json
Packagistpsr/http-message^1.0 || ^2.0composer.json
Packagistpsr/http-factory^1.0composer.json
Packagistpsr/http-server-handler^1.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistpsr/log^1.1 || ^2.0 || ^3.0composer.json
Packagistyiisoft/access^2.0composer.json
Packagistyiisoft/auth^3.3.0composer.json
Packagistyiisoft/cookies^1.2composer.json
Packagistyiisoft/session^3.0.2composer.json
Packagistyiisoft/http^1.2composer.json
All dependencies 25

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

RegistryPackageVersionRelation
Packagistpsr/event-dispatcher—direct
Packagistpsr/http-factory—direct
Packagistpsr/http-message—direct
Packagistpsr/http-server-handler—direct
Packagistpsr/http-server-middleware—direct
Packagistpsr/log—direct
Packagistyiisoft/access—direct
Packagistyiisoft/auth—direct
Packagistyiisoft/cookies—direct
Packagistyiisoft/http—direct
Packagistyiisoft/session—direct
Packagistbamarni/composer-bin-plugin—indirect
Packagistfriendsofphp/php-cs-fixer—indirect
Packagisthttpsoft/http-message—indirect
Packagistmaglnet/composer-require-checker—indirect
Packagistphp—indirect
Packagistphpunit/phpunit—indirect
Packagistrector/rector—indirect
Packagistroave/infection-static-analysis-plugin—indirect
Packagistshipmonk/composer-dependency-analyser—indirect
Packagistspatie/phpunit-watcher—indirect
Packagistvimeo/psalm—indirect
Packagistyiisoft/code-style—indirect
Packagistyiisoft/di—indirect
Packagistyiisoft/test-support—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.