Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 08:55 UTC

koriym / Koriym.NullObject

A NullObject generator

PHPMIT★ 3 stars⑂ 1 forksince Feb 2021View on GitHub ↗

koriym/Koriym.NullObject holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (73/100) and lowest on AI Readiness (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Akihito KoriyamaPersonal account
262 followers262 public repossince Dec 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistkoriym/null-object1.0.4119,88861149 days ago

Metrics by category

Vitality

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

45Weak · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
1.4/36Commit cadence — 2/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year6
human_commit_share1
days_since_last_push0
active_weeks_last_year2
How it's scored
27/27Ships releases — 6 releases published
0/36Release recency — latest release 1,149 days ago
12.6/27Release cadence — a release every ~191.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count6
latest_release_tag1.0.4
releases_from_tagsno
days_since_latest_release1,149
mean_days_between_releases191.8
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?

44Weak · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars3
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com
has_pull_request_templateno
How it's scored
67.7/80Monthly downloads — 119,888 downloads/month across packagist
4/20Registry dependents — 3 packages depend on it
Inputs used
packageskoriym/null-object
dependents3
ecosystemspackagist
total_downloads2,248,445
monthly_downloads119,888
unverified_packages_excluded—

Sustainability & Governance

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

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.959
How it's scored
42/42Issue resolution — 100% of issues closed
27.3/30PR acceptance — 10/11 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 4/7 approved changesets -- score normalized to 5
Inputs used
merged_prs10
open_issues0
closed_issues2
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs1
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
17.4/25Owner reach — 262 followers of koriym
25/25Track record — 262 public repos, account ~15 yr old
Inputs used
followers262
owner_typeUser
is_verified—
owner_loginkoriym
public_repos262
account_age_days5,816
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
4/35Publish recency — latest publish 1,149 days ago
20/20Version history — 6 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageskoriym/null-object
ecosystemspackagist
any_deprecatedno
min_days_since_publish1,149

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://packagist.org/packages/koriym/null-object
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicsnullobject
has_wikiyes
homepagehttps://packagist.org/packages/koriym/null-object
docs_sitehttps://packagist.org/packages/koriym/null-object
has_readmeyes
has_docs_dirno
has_descriptionyes

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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1/2.5CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 4/7 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 4 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.5/2.5License — license file detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): 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
advisories1
affected_packages1
assessed_packages59
unassessed_packages4
affected_by_severityhigh 1
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 59 resolved dependencies against OSV. 4 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
7.6/40Legible commit history — 14 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.143
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpcs.xml, phpstan.neon
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 98
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_dockerfileno
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 — 0/23 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes5,128
source_files_sampled23
oversized_source_files0

Key facts

3GitHub stars
2contributors
6commits, last 12 months
0days since last push
6releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 4.3 / 10
4.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-11-21 08:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 4/7 approved changesets -- score normalized to 5
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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 63

Full resolved dependency set from the GitHub dependency graph: 0 direct and 63 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.3.3indirect
Packagistamphp/parser1.1.1indirect
Packagistamphp/pipeline1.2.3indirect
Packagistamphp/process2.0.3indirect
Packagistamphp/serialization1.0.0indirect
Packagistamphp/socket2.3.1indirect
Packagistamphp/sync2.3.0indirect
Packagistbamarni/composer-bin-plugin—indirect
Packagistcomposer/pcre3.3.2indirect
Packagistcomposer/semver3.4.4indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistdanog/advanced-json-rpc3.2.3indirect
Packagistdaverandom/libdns2.1.0indirect
Packagistdealerdirect/phpcodesniffer-composer-installer1.2.0indirect
Packagistdnoegel/php-xdg-base-dir0.1.1indirect
Packagistdoctrine/annotations—indirect
Packagistdoctrine/coding-standard12.0.0indirect
Packagistdoctrine/deprecations1.1.5indirect
Packagistfelixfbecker/language-server-protocol1.5.3indirect
Packagistfidry/cpu-core-counter1.3.0indirect
Packagistkelunik/certificate1.1.3indirect
Packagistleague/uri7.8.0indirect
Packagistleague/uri-interfaces7.8.0indirect
Packagistnetresearch/jsonmapper5.0.0indirect
Packagistnikic/php-parser5.7.0indirect
Packagistpdepend/pdepend2.16.2indirect
Packagistphp—indirect
Packagistphpdocumentor/reflection-common2.2.0indirect
Packagistphpdocumentor/reflection-docblock6.0.1indirect
Packagistphpdocumentor/type-resolver2.0.0indirect
Packagistphpmd/phpmd2.15.0indirect
Packagistphpmetrics/phpmetrics2.9.1indirect
Packagistphpstan/phpdoc-parser2.3.1indirect
Packagistphpstan/phpstan1.12.32indirect
Packagistphpunit/phpunit—indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/http-factory1.1.0indirect
Packagistpsr/http-message2.0indirect
Packagistpsr/log3.0.2indirect
Packagistrevolt/event-loop1.0.8indirect
Packagistsebastian/diff7.0.0indirect
Packagistslevomat/coding-standard8.22.1indirect
Packagistspatie/array-to-xml3.4.4indirect
Packagistsquizlabs/php_codesniffer3.13.5indirect
Packagistsymfony/config7.4.3indirect
Packagistsymfony/console8.0.3indirect
Packagistsymfony/dependency-injection7.4.3indirect
Packagistsymfony/deprecation-contracts3.6.0indirect
Packagistsymfony/filesystem7.4.0indirect
Packagistsymfony/polyfill-ctype1.33.0indirect
Packagistsymfony/polyfill-intl-grapheme1.33.0indirect
Packagistsymfony/polyfill-intl-normalizer1.33.0indirect
Packagistsymfony/polyfill-mbstring1.33.0indirect
Packagistsymfony/polyfill-php841.33.0indirect
Packagistsymfony/service-contracts3.6.1indirect
Packagistsymfony/string8.0.1indirect
Packagistsymfony/var-exporter8.0.0indirect
Packagistvimeo/psalm6.14.3indirect
Packagistwebmozart/assert2.1.2indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 59 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 4 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
squizlabs/php_codesniffer3.13.5indirecthigh14.0.2

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.