Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 01:52 UTC

koriym / Koriym.NullObject

A NullObject generator

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

koriym/Koriym.NullObject holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (71/100) and lowest on Vitality (24/100). It was last updated 239 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Akihito KoriyamaPersonal account
262 followers257 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.492,64861084 days ago

Metrics by category

Vitality

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

24At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 239 days ago
0.7/36Commit cadence1/52 weeks with commits
7/18Commit volume5 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year5
human_commit_share1
days_since_last_push239
active_weeks_last_year1
How it's scored
27/27Ships releases6 releases published
0/36Release recencylatest release 1,084 days ago
12.6/27Release cadencea release every ~191.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count6
latest_release_tag1.0.4
releases_from_tagsno
days_since_latest_release1,084
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/60Stars3 stars
0/25Forks1 forks
0/15Watchers2 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.5Licenserecognized 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
66.2/80Monthly downloads92,648 downloads/month across packagist
4/20Registry dependents3 packages depend on it
Inputs used
packageskoriym/null-object
dependents3
ecosystemspackagist
total_downloads2,040,827
monthly_downloads92,648
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 factor1 contributor(s) cover half of all commits
0.9/22.5Commit distributiontop contributor authored 96% of commits
2.7/13.5Contributor breadth2 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.958
How it's scored
42/42Issue resolution100% of issues closed
27/30PR acceptance9/10 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 4/8 approved changesets -- score normalized to 5
Inputs used
merged_prs9
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.4/25Owner reach262 followers of koriym
25/25Track record257 public repos, account ~15 yr old
Inputs used
followers262
owner_typeUser
is_verified
owner_loginkoriym
public_repos257
account_age_days5,752
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
4/35Publish recencylatest publish 1,084 days ago
20/20Version history6 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskoriym/null-object
ecosystemspackagist
any_deprecatedno
min_days_since_publish1,084

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configphpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
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 sitehttps://packagist.org/packages/koriym/null-object
10/10Repository description
10/10Topics1 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-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.5/2.5CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 4/8 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 4 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.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
7.2/40Legible commit history13 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.135
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpcs.xml, phpstan.neon
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 96
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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 codePHP without a type-check config
55/55Manageable file sizes0/23 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes5,128
source_files_sampled23
oversized_source_files0

Key facts

3GitHub stars
2contributors
5commits, last 12 months
239days 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.2 / 10
4.2aggregate

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-18 01:52 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 4/8 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
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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-pluginindirect
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/annotationsindirect
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
Packagistphpindirect
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/phpunitindirect
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 statisticsPackagist.