Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-23 16:02 UTC

hirasso / focal-point-picker

Zero-dependency custom focal point picker for your WordPress images 🎯

JavaScript · PHPNo license detected★ 42 stars⑂ 6 forkssince Jun 2024View on GitHub ↗

hirasso/focal-point-picker holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Vitality (61/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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.

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)

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

Ownership

Rasso HilberPersonal account

55 followers56 public repossince Jun 2011

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
Packagist	hirasso/focal-point-picker	v1.4.0	2,159	16	327 days ago

Metrics by category

Vitality

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

61Moderate · 21% of overall

Development activity

55Moderate

How it's scored

36/36	Push recency — last push 0 days ago
1.4/36	Commit cadence — 2/52 weeks with commits
11.5/18	Commit volume — 18 commits in the last year
6/10	OpenSSF Scorecard: Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6

Inputs used

commits_last_year	18
human_commit_share	0.94
days_since_last_push	0
active_weeks_last_year	2

Release discipline

70Good

How it's scored

27/27	Ships releases — 16 releases published
16.2/36	Release recency — latest release 327 days ago
19.8/27	Release cadence — a release every ~51.4 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	16
latest_release_tag	v1.4.0
releases_from_tags	no
days_since_latest_release	327
mean_days_between_releases	51.4

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

Popularity & adoption

34At Risk

How it's scored

26.2/60	Stars — 42 stars
5.8/25	Forks — 6 forks
1.7/15	Watchers — 3 watchers

Inputs used

forks	6
stars	42
watchers	3
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

25At Risk

How it's scored

22.5/22.5	README
0/22.5	License — no license file detected
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	no
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

44Weak

How it's scored

44.5/80	Monthly downloads — 2,159 downloads/month across packagist
0/20	Registry dependents — 0 packages depend on it

Inputs used

packages	hirasso/focal-point-picker
dependents	0
ecosystems	packagist
total_downloads	12,807
monthly_downloads	2,159
unverified_packages_excluded	—

Sustainability & Governance

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

59Moderate · 23% of overall

Maintainer resilience (bus factor)

15Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5	Commit distribution — top contributor authored 97% of commits
2.7/13.5	Contributor breadth — 2 contributors
3/10	OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3

Inputs used

bus_factor	1
contributors_sampled	2
top_contributor_share	0.971

Issue & PR responsiveness

85Excellent

How it's scored

42/42	Issue resolution — 100% of issues closed
28.2/30	PR acceptance — 16/17 decided PRs merged
13/13	Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15	OpenSSF Scorecard: Code-Review — Found 1/10 approved changesets -- score normalized to 1

Inputs used

merged_prs	16
open_issues	0
closed_issues	4
prs_merged_7d	2
prs_decided_7d	2
prs_merged_30d	2
prs_decided_30d	2
issue_closed_ratio	1
closed_unmerged_prs	1
first_time_authors_30d	1
first_time_prs_merged_30d	1
first_time_prs_decided_30d	1

Ownership & stewardship

59Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
12.6/25	Owner reach — 55 followers of hirasso
24.8/25	Track record — 56 public repos, account ~15 yr old

Inputs used

followers	55
owner_type	User
is_verified	—
owner_login	hirasso
public_repos	56
account_age_days	5,571

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

91Excellent

How it's scored

25/25	Published & resolvable — 1 package(s) on packagist
26/35	Publish recency — latest publish 327 days ago
20/20	Version history — 16 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	hirasso/focal-point-picker
ecosystems	packagist
any_deprecated	no
min_days_since_publish	327

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall

Engineering practices

46Weak

How it's scored

24/24	CI workflows — 1 workflow(s)
0/24	Tests present
16/16	Linter config — phpstan.neon
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	yes
has_tests	no
has_editorconfig	yes
has_linter_config	yes
has_precommit_config	no

Documentation

60Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
10/10	Topics — 2 topics
10/10	Wiki

Inputs used

topics	focal-point, wordpress
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

44Weak · 16% of overall

Security posture

30At Risk

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5	Code-Review — Found 1/10 approved changesets -- score normalized to 1
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
0/2.5	License — license file not detected
4.5/7.5	Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	13
scorecard_version	v5.5.0
checks_inconclusive	5
scorecard_aggregate	3

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	13
affected_packages	7
assessed_packages	160
unassessed_packages	0
affected_by_severity	high 4, moderate 3
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 160 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.

51Moderate · 4% of overall

Agent context & guidance

55Moderate

How it's scored

45/45	Agent instructions — AGENTS.md
0/15	Machine-readable docs (llms.txt)
10.2/40	Legible commit history — 18 of 94 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.191
agent_instruction_files	AGENTS.md
agent_instruction_max_bytes	390

Verify loop (build / test / typecheck)

36Weak

How it's scored

0/18	One-command bootstrap
0/22	Automated tests
11/11	Lint / format config — phpstan.neon
11/11	Static type checking — jsconfig.json
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	no
lockfiles	composer.lock, pnpm-lock.yaml
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	jsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

82Excellent

How it's scored

27/45	Type-checkable code — JavaScript with type-check config (jsconfig.json)
55/55	Manageable file sizes — 0/11 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	16,510
source_files_sampled	11
oversized_source_files	0

Key facts

42GitHub stars

2contributors

18commits, last 12 months

0days since last push

16releases

1bus factor

0open issues

npm, Packagistpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 6 ⇿

0Stars

6Forks

1Releases

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.

Major 0Minor 1Patch 0

Each point covers 2 days.

OpenSSF Scorecard 3.0 / 10

3.0aggregate

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-23 16:02 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
1	Code-Review	Found 1/10 approved changesets -- score normalized to 1
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
0	License	license file not detected
6	Maintained	8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
10	Vulnerabilities	0 existing vulnerabilities detected

All dependencies 160

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

Registry	Package	Version	Relation
npm	@babel/runtime	`7.26.0`	indirect
npm	@changesets/apply-release-plan	`7.0.7`	indirect
npm	@changesets/assemble-release-plan	`6.0.5`	indirect
npm	@changesets/changelog-git	`0.2.0`	indirect
npm	@changesets/cli	`2.27.11`	indirect
npm	@changesets/config	`3.0.5`	indirect
npm	@changesets/errors	`0.2.0`	indirect
npm	@changesets/get-dependents-graph	`2.1.2`	indirect
npm	@changesets/get-release-plan	`4.0.6`	indirect
npm	@changesets/get-version-range-type	`0.4.0`	indirect
npm	@changesets/git	`3.0.2`	indirect
npm	@changesets/logger	`0.1.1`	indirect
npm	@changesets/parse	`0.4.0`	indirect
npm	@changesets/pre	`2.0.1`	indirect
npm	@changesets/read	`0.6.2`	indirect
npm	@changesets/should-skip-package	`0.1.1`	indirect
npm	@changesets/types	`4.1.0`	indirect
npm	@changesets/types	`6.0.0`	indirect
npm	@changesets/write	`0.3.2`	indirect
npm	@manypkg/find-root	`1.1.0`	indirect
npm	@manypkg/get-packages	`1.1.3`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@types/node	`12.20.55`	indirect
npm	ansi-colors	`4.1.3`	indirect
npm	ansi-escapes	`6.2.1`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.0.1`	indirect
npm	ansi-styles	`6.2.1`	indirect
npm	argparse	`1.0.10`	indirect
npm	array-union	`2.1.0`	indirect
npm	better-path-resolve	`1.0.0`	indirect
npm	braces	`3.0.3`	indirect
npm	chalk	`5.3.0`	indirect
npm	chardet	`0.7.0`	indirect
npm	ci-info	`3.9.0`	indirect
npm	cli-cursor	`4.0.0`	indirect
npm	cli-truncate	`4.0.0`	indirect
npm	colorette	`2.0.20`	indirect
npm	commander	`12.1.0`	indirect
npm	cross-spawn	`7.0.3`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.3.5`	indirect
npm	detect-indent	`6.1.0`	indirect
npm	dir-glob	`3.0.1`	indirect
npm	emoji-regex	`10.3.0`	indirect
npm	enquirer	`2.4.1`	indirect
npm	esprima	`4.0.1`	indirect
npm	eventemitter3	`5.0.1`	indirect
npm	execa	`8.0.1`	indirect
npm	extendable-error	`0.1.7`	indirect
npm	external-editor	`3.1.0`	indirect
npm	fast-glob	`3.3.3`	indirect
npm	fastq	`1.18.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`4.1.0`	indirect
npm	fs-extra	`7.0.1`	indirect
npm	fs-extra	`8.1.0`	indirect
npm	get-east-asian-width	`1.2.0`	indirect
npm	get-stream	`8.0.1`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	globby	`11.1.0`	indirect
npm	graceful-fs	`4.2.11`	indirect
npm	human-id	`1.0.2`	indirect
npm	human-signals	`5.0.0`	indirect
npm	husky	`9.1.1`	indirect
npm	iconv-lite	`0.4.24`	indirect
npm	ignore	`5.3.2`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`4.0.0`	indirect
npm	is-fullwidth-code-point	`5.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-stream	`3.0.0`	indirect
npm	is-subdir	`1.2.0`	indirect
npm	is-windows	`1.0.2`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-yaml	`3.14.1`	indirect
npm	jsonfile	`4.0.0`	indirect
npm	lilconfig	`3.1.2`	indirect
npm	lint-staged	`15.2.7`	indirect
npm	listr2	`8.2.3`	indirect
npm	locate-path	`5.0.0`	indirect
npm	lodash.startcase	`4.4.0`	indirect
npm	log-update	`6.0.0`	indirect
npm	merge-stream	`2.0.0`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.7`	indirect
npm	micromatch	`4.0.8`	indirect
npm	mimic-fn	`2.1.0`	indirect
npm	mimic-fn	`4.0.0`	indirect
npm	mri	`1.2.0`	indirect
npm	ms	`2.1.2`	indirect
npm	npm-run-path	`5.3.0`	indirect
npm	onetime	`5.1.2`	indirect
npm	onetime	`6.0.0`	indirect
npm	os-tmpdir	`1.0.2`	indirect
npm	outdent	`0.5.0`	indirect
npm	p-filter	`2.1.0`	indirect
npm	p-limit	`2.3.0`	indirect
npm	p-locate	`4.1.0`	indirect
npm	p-map	`2.1.0`	indirect
npm	p-try	`2.2.0`	indirect
npm	package-manager-detector	`0.2.8`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-key	`4.0.0`	indirect
npm	path-type	`4.0.0`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	pidtree	`0.6.0`	indirect
npm	pify	`4.0.1`	indirect
npm	prettier	`2.8.8`	indirect
npm	prettier	`3.3.3`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	read-yaml-file	`1.1.0`	indirect
npm	regenerator-runtime	`0.14.1`	indirect
npm	resolve-from	`5.0.0`	indirect
npm	restore-cursor	`4.0.0`	indirect
npm	reusify	`1.0.4`	indirect
npm	rfdc	`1.4.1`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	semver	`7.6.3`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`3.0.7`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	slash	`3.0.0`	indirect
npm	slice-ansi	`5.0.0`	indirect
npm	slice-ansi	`7.1.0`	indirect
npm	spawndamnit	`3.0.1`	indirect
npm	sprintf-js	`1.0.3`	indirect
npm	string-argv	`0.3.2`	indirect
npm	string-width	`7.2.0`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.1.0`	indirect
npm	strip-bom	`3.0.0`	indirect
npm	strip-final-newline	`3.0.0`	indirect
npm	term-size	`2.2.1`	indirect
npm	tmp	`0.0.33`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	universalify	`0.1.2`	indirect
npm	which	`2.0.2`	indirect
npm	wrap-ansi	`9.0.0`	indirect
npm	yaml	`2.4.5`	indirect
Packagist	composer/installers	`2.3.0`	indirect
Packagist	laravel/pint	`1.25.1`	indirect
Packagist	phpstan/phpstan	`2.1.31`	indirect
Packagist	roots/wordpress	`6.8.3`	indirect
Packagist	roots/wordpress-core-installer	`3.0.0`	indirect
Packagist	roots/wordpress-no-content	`6.8.3`	indirect
Packagist	symfony/finder	`7.3.5`	indirect
Packagist	symfony/polyfill-mbstring	`1.30.0`	indirect
Packagist	symfony/var-dumper	`7.1.2`	indirect
Packagist	wp-cli/mustache	`2.14.99`	indirect
Packagist	wp-cli/mustangostang-spyc	`0.6.3`	indirect
Packagist	wp-cli/php-cli-tools	`0.12.6`	indirect
Packagist	wp-cli/wp-cli	`2.12.0`	indirect

Dependency advisories 7

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

Package	Version	Relation	Severity	Advisories	Fixed in
cross-spawn	`7.0.3`	indirect	high	1	`7.0.5`
js-yaml	`3.14.1`	indirect	high	5	`4.3.2`
picomatch	`2.3.1`	indirect	high	2	`4.0.4`
tmp	`0.0.33`	indirect	high	2	`0.2.6`
@babel/runtime	`7.26.0`	indirect	moderate	1	`8.0.0-alpha.17`
micromatch	`4.0.7`	indirect	moderate	1	`4.0.8`
yaml	`2.4.5`	indirect	moderate	1	`2.8.3`

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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records