Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 03:51 UTC

Lendable / message

PHPMIT★ 1 star⑂ 0 forkssince Feb 2024View on GitHub ↗

Lendable/message holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (77/100) and lowest on Community & Adoption (33/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

Lendable LtdOrganization · verified domain
80 followers33 public repossince Jan 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistlendable/message2.2.04,6349156 days ago

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
11.8/36Commit cadence — 17/52 weeks with commits
15.5/18Commit volume — 52 commits in the last year
10/10OpenSSF Scorecard: Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year52
human_commit_share0.13
days_since_last_push1
active_weeks_last_year17
How it's scored
27/27Ships releases — 9 releases published
27/36Release recency — latest release 156 days ago
19.8/27Release cadence — a release every ~96.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tag2.2.0
releases_from_tagsno
days_since_latest_release156
mean_days_between_releases96.7
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?

33At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
8.4/15Watchers — 33 watchers
Inputs used
forks0
stars1
watchers33
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
48.9/80Monthly downloads — 4,634 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packageslendable/message
dependents0
ecosystemspackagist
total_downloads116,981
monthly_downloads4,634
unverified_packages_excluded—

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.5/22.5Commit distribution — top contributor authored 67% of commits
9.5/13.5Contributor breadth — 7 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.667
How it's scored
28/42Issue resolution — 67% of issues closed
24.8/30PR acceptance — 210/254 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs210
open_issues1
closed_issues2
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d2
issue_closed_ratio0.667
closed_unmerged_prs44
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
13.7/25Owner reach — 80 followers of Lendable
23.2/25Track record — 33 public repos, account ~11 yr old
Inputs used
followers80
owner_typeOrganization
is_verifiedyes
owner_loginLendable
public_repos33
account_age_days4,324

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 156 days ago
20/20Version history — 9 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslendable/message
ecosystemspackagist
any_deprecatedno
min_days_since_publish156

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 26 out of 30 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

30At Risk
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
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?

65Good · 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.5CI-Tests — 26 out of 30 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages59
unassessed_packages1
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 59 resolved dependencies against OSV. 1 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.php, phpstan.neon
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 86 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.86
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/68 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes14,702
source_files_sampled68
oversized_source_files0

Key facts

1GitHub stars
7contributors
52commits, last 12 months
1days since last push
9releases
1bus factor
1open issues
Packagistpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-16 03:51 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
8CI-Tests26 out of 30 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistramsey/uuid^4.7composer.json
All dependencies 60

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

RegistryPackageVersionRelation
Packagistramsey/uuid4.7.6direct
Packagistbrick/math0.12.1indirect
Packagistergebnis/composer-normalize2.56.0indirect
Packagistergebnis/json1.6.0indirect
Packagistergebnis/json-normalizer4.12.0indirect
Packagistergebnis/json-pointer3.8.0indirect
Packagistergebnis/json-printer3.8.1indirect
Packagistergebnis/json-schema-validator4.5.1indirect
Packagistergebnis/phpstan-rules2.17.0indirect
Packagistergebnis/version1.5.0indirect
Packagistjustinrainbow/json-schema6.8.0indirect
Packagistlendable/composer-license-checker1.4.1indirect
Packagistlendable/phpunit-extensions0.5.0indirect
Packagistlocalheinz/diff1.3.0indirect
Packagistmarc-mabe/php-enum4.7.2indirect
Packagistmyclabs/deep-copy1.14.0indirect
Packagistnikic/php-parser5.9.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphp—indirect
Packagistphp-cs-fixer/shim3.95.29indirect
Packagistphpstan/phpstan2.3.5indirect
Packagistphpstan/phpstan-deprecation-rules2.0.5indirect
Packagistphpstan/phpstan-phpunit2.1.1indirect
Packagistphpstan/phpstan-strict-rules2.1.1indirect
Packagistphpunit/php-code-coverage14.5.2indirect
Packagistphpunit/php-file-iterator7.0.2indirect
Packagistphpunit/php-invoker7.0.0indirect
Packagistphpunit/php-text-template6.0.1indirect
Packagistphpunit/php-timer9.0.0indirect
Packagistphpunit/phpunit13.4.6indirect
Packagistpsr/container2.0.2indirect
Packagistramsey/collection2.0.0indirect
Packagistrector/rector2.8.4indirect
Packagistsebastian/cli-parser5.0.1indirect
Packagistsebastian/comparator8.4.0indirect
Packagistsebastian/complexity6.0.0indirect
Packagistsebastian/diff9.0.1indirect
Packagistsebastian/environment9.3.3indirect
Packagistsebastian/exporter8.2.1indirect
Packagistsebastian/file-filter1.0.0indirect
Packagistsebastian/git-state1.1.0indirect
Packagistsebastian/global-state9.0.1indirect
Packagistsebastian/lines-of-code5.0.2indirect
Packagistsebastian/object-enumerator8.1.0indirect
Packagistsebastian/object-reflector6.0.0indirect
Packagistsebastian/recursion-context8.0.1indirect
Packagistsebastian/type7.0.2indirect
Packagistsebastian/version7.0.1indirect
Packagiststaabm/side-effects-detector1.0.5indirect
Packagistsymfony/console8.1.1indirect
Packagistsymfony/deprecation-contracts3.5.1indirect
Packagistsymfony/polyfill-ctype1.31.0indirect
Packagistsymfony/polyfill-intl-grapheme1.38.1indirect
Packagistsymfony/polyfill-intl-normalizer1.31.0indirect
Packagistsymfony/polyfill-mbstring1.31.0indirect
Packagistsymfony/polyfill-php851.38.1indirect
Packagistsymfony/process8.1.0indirect
Packagistsymfony/service-contracts3.5.1indirect
Packagistsymfony/string8.1.0indirect
Dependency advisories 0

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: 0 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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.