Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-20 19:58 UTC

wp-hooks / wordpress-core-hooks

WordPress core actions and filters as JSON

ShellGPL-3.0★ 126 stars⑂ 6 forkssince Oct 2019View on GitHub ↗

wp-hooks/wordpress-core-hooks holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Vitality (67/100) and lowest on AI Readiness (15/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 55 is calibrated to 57 on the published index scale (record calibration 2026-08-02).

Ownership

WP HooksOrganization

17 followers5 public repossince Jul 2022

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	@wp-hooks/wordpress-core	1.13.0	59	13	0 days ago	wordpress
Packagist	wp-hooks/wordpress-core	1.12.0	33,776	47	90 days ago	—

Metrics by category

Vitality

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

67Good · 21% of overall

Development activity

55Moderate

How it's scored

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

Inputs used

commits_last_year	30
human_commit_share	1
days_since_last_push	0
active_weeks_last_year	5

Release discipline

84Excellent

How it's scored

27/27	Ships releases — 28 releases published
36/36	Release recency — latest release 0 days ago
12.6/27	Release cadence — a release every ~123.1 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	28
latest_release_tag	1.13.0
releases_from_tags	no
days_since_latest_release	0
mean_days_between_releases	123.1

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?

51Moderate · 17% of overall

Popularity & adoption

44Weak

How it's scored

34/60	Stars — 126 stars
5.8/25	Forks — 6 forks
4.3/15	Watchers — 7 watchers

Inputs used

forks	6
stars	126
watchers	7
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (GPL-3.0)
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	yes
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)

65Good

How it's scored

60.4/80	Monthly downloads — 33,835 downloads/month across npm, packagist
4.7/20	Registry dependents — 4 packages depend on it

Inputs used

packages	@wp-hooks/wordpress-core, wp-hooks/wordpress-core
dependents	4
ecosystems	npm, packagist
total_downloads	496,217
monthly_downloads	33,835
unverified_packages_excluded	—

Sustainability & Governance

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

62Moderate · 23% of overall

Maintainer resilience (bus factor)

23At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5	Commit distribution — top contributor authored 96% of commits
2.7/13.5	Contributor breadth — 2 contributors
10/10	OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	2
top_contributor_share	0.962

Issue & PR responsiveness

75Good

How it's scored

42/42	Issue resolution — 100% of issues closed
22.9/30	PR acceptance — 13/17 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/23 approved changesets -- score normalized to 0

Inputs used

merged_prs	13
open_issues	0
closed_issues	12
prs_merged_7d	1
prs_decided_7d	1
prs_merged_30d	1
prs_decided_30d	1
issue_closed_ratio	1
closed_unmerged_prs	4
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

66Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain — verified-domain status not read for this organization
9/25	Owner reach — 17 followers of wp-hooks
13.9/25	Track record — 5 public repos, account ~4 yr old

Inputs used

followers	17
owner_type	Organization
is_verified	—
owner_login	wp-hooks
public_repos	5
account_age_days	1,509

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

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 2 package(s) on npm, packagist
35/35	Publish recency — latest publish 0 days ago
20/20	Version history — 47 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	@wp-hooks/wordpress-core, wp-hooks/wordpress-core
ecosystems	npm, packagist
any_deprecated	no
min_days_since_publish	0

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall

Engineering practices

44Weak

How it's scored

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

Inputs used

has_ci	yes
has_tests	no
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://packagist.org/packages/wp-hooks/wordpress-core
10/10	Repository description
10/10	Topics — 1 topics
0/10	Wiki

Inputs used

topics	wordpress
has_wiki	no
homepage	https://packagist.org/packages/wp-hooks/wordpress-core
docs_site	https://packagist.org/packages/wp-hooks/wordpress-core
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?

45Weak · 16% of overall

Security posture

31At 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
2.5/2.5	CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/23 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 8 contributing companies or organizations
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
1.5/7.5	Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
5/5	SAST — SAST tool is run on all commits
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
0/7.5	Vulnerabilities — 23 existing vulnerabilities detected

Inputs used

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

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	24
affected_packages	12
assessed_packages	125
unassessed_packages	3
affected_by_severity	critical 2, high 8, moderate 2
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 125 resolved dependencies against OSV. 3 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.

15Critical · 4% of overall

Agent context & guidance

1Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
0.5/40	Legible commit history — 1 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.01
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

11Critical

How it's scored

0/18	One-command bootstrap
0/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
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	package-lock.json
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
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

55Moderate

How it's scored

0/45	Type-checkable code — Shell without a type-check config
55/55	Manageable file sizes — 0/1 source files over 60KB

Inputs used

primary_language	Shell
largest_source_bytes	1,855
source_files_sampled	1
oversized_source_files	0

Key facts

126GitHub stars

2contributors

30commits, last 12 months

0days since last push

28releases

1bus factor

0open issues

npm, Packagistpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
deps.dev does not index npm:@wp-hooks/wordpress-core@1.13.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 6 ⇿

0Stars

6Forks

25Releases

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 1Minor 15Patch 9

Each point covers 6 days.

OpenSSF Scorecard 3.1 / 10

3.1aggregate

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-20 19:58 UTC

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

All dependencies 128

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

Registry	Package	Version	Relation
npm	abbrev	`1.1.1`	indirect
npm	ajv	`5.5.2`	indirect
npm	ajv	`6.12.6`	indirect
npm	ajv-cli	`3.3.0`	indirect
npm	ajv-pack	`0.3.1`	indirect
npm	ansi-styles	`3.2.1`	indirect
npm	argparse	`1.0.10`	indirect
npm	balanced-match	`1.0.0`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	call-bind	`1.0.2`	indirect
npm	chalk	`2.4.2`	indirect
npm	co	`4.6.0`	indirect
npm	color-convert	`1.9.3`	indirect
npm	color-name	`1.1.3`	indirect
npm	commander	`2.20.3`	indirect
npm	concat-map	`0.0.1`	indirect
npm	config-chain	`1.1.12`	indirect
npm	cross-spawn	`6.0.5`	indirect
npm	define-properties	`1.1.4`	indirect
npm	editorconfig	`0.15.3`	indirect
npm	error-ex	`1.3.2`	indirect
npm	es-abstract	`1.20.4`	indirect
npm	es-to-primitive	`1.2.1`	indirect
npm	escape-string-regexp	`1.0.5`	indirect
npm	esprima	`4.0.1`	indirect
npm	fast-deep-equal	`1.1.0`	indirect
npm	fast-deep-equal	`2.0.1`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-patch	`2.2.1`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	function-bind	`1.1.1`	indirect
npm	function.prototype.name	`1.1.5`	indirect
npm	functions-have-names	`1.2.3`	indirect
npm	get-intrinsic	`1.1.3`	indirect
npm	get-symbol-description	`1.0.0`	indirect
npm	glob	`7.1.6`	indirect
npm	graceful-fs	`4.2.10`	indirect
npm	has	`1.0.3`	indirect
npm	has-bigints	`1.0.2`	indirect
npm	has-flag	`3.0.0`	indirect
npm	has-property-descriptors	`1.0.0`	indirect
npm	has-symbols	`1.0.3`	indirect
npm	has-tostringtag	`1.0.0`	indirect
npm	hosted-git-info	`2.8.9`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	ini	`1.3.5`	indirect
npm	internal-slot	`1.0.3`	indirect
npm	is-arrayish	`0.2.1`	indirect
npm	is-bigint	`1.0.4`	indirect
npm	is-boolean-object	`1.1.2`	indirect
npm	is-callable	`1.2.7`	indirect
npm	is-core-module	`2.11.0`	indirect
npm	is-date-object	`1.0.5`	indirect
npm	is-negative-zero	`2.0.2`	indirect
npm	is-number-object	`1.0.7`	indirect
npm	is-regex	`1.1.4`	indirect
npm	is-shared-array-buffer	`1.0.2`	indirect
npm	is-string	`1.0.7`	indirect
npm	is-symbol	`1.0.4`	indirect
npm	is-weakref	`1.0.2`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-beautify	`1.13.0`	indirect
npm	js-yaml	`3.14.0`	indirect
npm	json-parse-better-errors	`1.0.2`	indirect
npm	json-schema-migrate	`0.2.0`	indirect
npm	json-schema-traverse	`0.3.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json5	`2.1.3`	indirect
npm	load-json-file	`4.0.0`	indirect
npm	lru-cache	`4.1.5`	indirect
npm	memorystream	`0.3.1`	indirect
npm	minimatch	`3.0.4`	indirect
npm	minimist	`1.2.5`	indirect
npm	mkdirp	`1.0.4`	indirect
npm	nice-try	`1.0.5`	indirect
npm	nopt	`5.0.0`	indirect
npm	normalize-package-data	`2.5.0`	indirect
npm	npm-run-all	`4.1.5`	indirect
npm	object-inspect	`1.12.2`	indirect
npm	object-keys	`1.1.1`	indirect
npm	object.assign	`4.1.4`	indirect
npm	once	`1.4.0`	indirect
npm	parse-json	`4.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-key	`2.0.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	path-type	`3.0.0`	indirect
npm	pidtree	`0.3.1`	indirect
npm	pify	`3.0.0`	indirect
npm	proto-list	`1.2.4`	indirect
npm	pseudomap	`1.0.2`	indirect
npm	punycode	`2.1.1`	indirect
npm	read-pkg	`3.0.0`	indirect
npm	regexp.prototype.flags	`1.4.3`	indirect
npm	require-from-string	`1.2.1`	indirect
npm	resolve	`1.22.1`	indirect
npm	safe-regex-test	`1.0.0`	indirect
npm	semver	`5.7.1`	indirect
npm	shebang-command	`1.2.0`	indirect
npm	shebang-regex	`1.0.0`	indirect
npm	shell-quote	`1.7.4`	indirect
npm	side-channel	`1.0.4`	indirect
npm	sigmund	`1.0.1`	indirect
npm	spdx-correct	`3.1.1`	indirect
npm	spdx-exceptions	`2.3.0`	indirect
npm	spdx-expression-parse	`3.0.1`	indirect
npm	spdx-license-ids	`3.0.12`	indirect
npm	sprintf-js	`1.0.3`	indirect
npm	string.prototype.padend	`3.1.4`	indirect
npm	string.prototype.trimend	`1.0.6`	indirect
npm	string.prototype.trimstart	`1.0.6`	indirect
npm	strip-bom	`3.0.0`	indirect
npm	supports-color	`5.5.0`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	unbox-primitive	`1.0.2`	indirect
npm	uri-js	`4.4.0`	indirect
npm	validate-npm-package-license	`3.0.4`	indirect
npm	which	`1.3.1`	indirect
npm	which-boxed-primitive	`1.0.2`	indirect
npm	wrappy	`1.0.2`	indirect
npm	yallist	`2.1.2`	indirect
Packagist	erusev/parsedown	`—`	indirect
Packagist	oomphinc/composer-installers-extender	`—`	indirect
Packagist	roots/wordpress-core-installer	`—`	indirect
Packagist	roots/wordpress-full	`7.1`	indirect
Packagist	wp-hooks/generator	`1.0.0`	indirect

Dependency advisories 12

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

Package	Version	Relation	Severity	Advisories	Fixed in
minimist	`1.2.5`	indirect	critical	1	`1.2.6`
shell-quote	`1.7.4`	indirect	critical	2	`1.9.0`
brace-expansion	`1.1.11`	indirect	high	5	`5.0.9`
cross-spawn	`6.0.5`	indirect	high	1	`7.0.5`
fast-json-patch	`2.2.1`	indirect	high	1	`3.1.1`
ini	`1.3.5`	indirect	high	1	`1.3.6`
js-yaml	`3.14.0`	indirect	high	4	`4.3.1`
json5	`2.1.3`	indirect	high	1	`2.2.2`
minimatch	`3.0.4`	indirect	high	4	`10.2.3`
semver	`5.7.1`	indirect	high	1	`7.5.2`
ajv	`5.5.2`	indirect	moderate	2	`8.18.0`
ajv	`6.12.6`	indirect	moderate	1	`8.18.0`

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 — npm, Packagist.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records