Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-31 12:02 UTC

minvws / horsebattery

A password generator inspired by https://xkcd.com/936/

PHPEUPL-1.2★ 10 stars⑂ 1 forksince Jan 2022View on GitHub ↗

minvws/horsebattery holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (83/100) and lowest on AI Readiness (47/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

164 followers190 public repossince May 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistminvws/horsebatteryv2.0.07,0347128 days agogeneratorsecuritypassword

Metrics by category

Vitality

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

54Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.1/36Commit cadence3/52 weeks with commits
7/18Commit volume5 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year5
human_commit_share0.93
days_since_last_push0
active_weeks_last_year3
How it's scored
27/27Ships releases5 releases published
27/36Release recencylatest release 128 days ago
5.4/27Release cadencea release every ~382.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tagv2.0.0
releases_from_tagsno
days_since_latest_release128
mean_days_between_releases382.3
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?

52Moderate · 17% of overall
How it's scored
15.5/60Stars10 stars
0/25Forks1 forks
6.5/15Watchers16 watchers
Inputs used
forks1
stars10
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (EUPL-1.2)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
51.3/80Monthly downloads7,034 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesminvws/horsebattery
dependents1
ecosystemspackagist
total_downloads113,879
monthly_downloads7,034
unverified_packages_excluded

Sustainability & Governance

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

83Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
15.6/22.5Commit distributiontop contributor authored 31% of commits
13.5/13.5Contributor breadth13 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled13
top_contributor_share0.306
How it's scored
14/42Issue resolution33% of issues closed
30/30PR acceptance26/26 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs26
open_issues2
closed_issues1
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.333
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
15.9/25Owner reach164 followers of minvws
25/25Track record190 public repos, account ~6 yr old
Inputs used
followers164
owner_typeOrganization
is_verifiedyes
owner_loginminvws
public_repos190
account_age_days2,294

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 128 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesminvws/horsebattery
ecosystemspackagist
any_deprecatedno
min_days_since_publish128

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter configphpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicsicore
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

71Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 14 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate6.4
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 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_packages31
unassessed_packages0
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 31 resolved dependencies against OSV. 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 instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30.2/40Legible commit history30 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.566
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 57
8/8Automated maintenance4 of the last 57 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
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.07
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/8 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes2,415
source_files_sampled8
oversized_source_files0

Key facts

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

Data collection warnings

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

More detail

OpenSSF Scorecard 6.4 / 10
6.4aggregate

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-08-31 12:02 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
0CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 14 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate 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
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 31

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

RegistryPackageVersionRelation
Packagisthamcrest/hamcrest-php2.1.1indirect
Packagistmockery/mockery1.6.12indirect
Packagistmyclabs/deep-copy1.13.4indirect
Packagistnikic/php-parser5.7.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpstan/phpstan2.1.51indirect
Packagistphpunit/php-code-coverage14.1.6indirect
Packagistphpunit/php-file-iterator7.0.0indirect
Packagistphpunit/php-invoker7.0.0indirect
Packagistphpunit/php-text-template6.0.0indirect
Packagistphpunit/php-timer9.0.0indirect
Packagistphpunit/phpunit13.1.7indirect
Packagistrector/rector2.4.2indirect
Packagistsebastian/cli-parser5.0.0indirect
Packagistsebastian/comparator8.1.2indirect
Packagistsebastian/complexity6.0.0indirect
Packagistsebastian/diff8.1.0indirect
Packagistsebastian/environment9.3.0indirect
Packagistsebastian/exporter8.0.2indirect
Packagistsebastian/git-state1.0.0indirect
Packagistsebastian/global-state9.0.0indirect
Packagistsebastian/lines-of-code5.0.0indirect
Packagistsebastian/object-enumerator8.0.0indirect
Packagistsebastian/object-reflector6.0.0indirect
Packagistsebastian/recursion-context8.0.0indirect
Packagistsebastian/type7.0.0indirect
Packagistsebastian/version7.0.0indirect
Packagistsquizlabs/php_codesniffer4.0.1indirect
Packagiststaabm/side-effects-detector1.0.5indirect
Packagisttheseer/tokenizer2.0.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 31 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
squizlabs/php_codesniffer4.0.1indirecthigh14.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.