Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 09:30 UTC

scionoftech / webp-converter

A small node.js library for converting any image to webp file format or converting webp image to any image file format.

CMIT★ 241 stars⑂ 46 forkssince Sep 2015View on GitHub ↗

#webp-converter #webp-images #gif2webp #dwebp #cwebp

scionoftech/webp-converter holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on AI Readiness (68/100) and lowest on Vitality (21/100). It was last updated 31 days ago. A single contributor accounts for most of its recent work.

overall / 100

Weak

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

Ownership

Sai Kumar YavaPersonal account

34 followers62 public repossince Jun 2015

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	Tags
npm	webp-converter	3.0.1	42,238	28	31 days ago	webp webpconverter webp-converter cwebp dwebp gif2webp webpmux

Metrics by category

Vitality

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

21At Risk · 21% of overall

Development activity

35Weak

How it's scored

18/36	Push recency — last push 31 days ago
0.7/36	Commit cadence — 1/52 weeks with commits
6.3/18	Commit volume — 4 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 4 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	4
human_commit_share	0.977
days_since_last_push	31
active_weeks_last_year	1

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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?

65Good · 17% of overall

Popularity & adoption

52Moderate

How it's scored

38.6/60	Stars — 241 stars
13.8/25	Forks — 46 forks
0/15	Watchers — 2 watchers

Inputs used

forks	46
stars	241
watchers	2
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

70Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/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	yes
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

77Good

How it's scored

61.7/80	Monthly downloads — 42,238 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	webp-converter
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	42,238
unverified_packages_excluded	—

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

48Weak · 23% of overall

Maintainer resilience (bus factor)

10Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

40Weak

How it's scored

31.2/42	Issue resolution — 74% of issues closed
3.5/30	PR acceptance — 2/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/27 approved changesets -- score normalized to 0

Inputs used

merged_prs	2
open_issues	10
closed_issues	29
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.744
closed_unmerged_prs	15
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

58Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
11.1/25	Owner reach — 34 followers of scionoftech
25/25	Track record — 62 public repos, account ~11 yr old

Inputs used

followers	34
owner_type	User
is_verified	—
owner_login	scionoftech
public_repos	62
account_age_days	4,094

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

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	webp-converter
ecosystems	npm
any_deprecated	no
min_days_since_publish	31

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall

Engineering practices

24At Risk

How it's scored

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

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

85Excellent

How it's scored

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

Inputs used

topics	webp-converter, webp-images, gif2webp, dwebp, cwebp
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

47Weak · 16% of overall

Security posture

34At Risk

How it's scored

0/7.5	Binary-Artifacts — binaries present in source code
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 2 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/7.5	Code-Review — Found 0/27 approved changesets -- score normalized to 0
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10	Dangerous-Workflow — no data
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 4 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
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
6/7.5	Vulnerabilities — 2 existing vulnerabilities detected

Inputs used

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

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	2
affected_packages	2
assessed_packages	136
unassessed_packages	0
affected_by_severity	high 1, low 1
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 136 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.

68Good · 4% of overall

Agent context & guidance

49Weak

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.07
agent_instruction_files	CLAUDE.md
agent_instruction_max_bytes	3,858

Verify loop (build / test / typecheck)

57Moderate

How it's scored

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

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0.023

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

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — C (statically typed)
55/55	Manageable file sizes — 0/49 source files over 60KB

Inputs used

primary_language	C
largest_source_bytes	29,061
source_files_sampled	49
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	—
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

241GitHub stars

1contributors

4commits, last 12 months

31days since last push

0releases

1bus factor

10open issues

npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 46 ⇿

0Stars

46Forks

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.

Each point covers 10 days.

OpenSSF Scorecard 3.4 / 10

3.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-28 09:30 UTC

0	Binary-Artifacts	binaries present in source code
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 2 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
0	Code-Review	Found 0/27 approved changesets -- score normalized to 0
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
n/a	Dangerous-Workflow	no workflows found
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	4 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
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
8	Vulnerabilities	2 existing vulnerabilities detected

All dependencies 136

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

Registry	Package	Version	Relation
npm	@esbuild/aix-ppc64	`0.27.7`	indirect
npm	@esbuild/android-arm	`0.27.7`	indirect
npm	@esbuild/android-arm64	`0.27.7`	indirect
npm	@esbuild/android-x64	`0.27.7`	indirect
npm	@esbuild/darwin-arm64	`0.27.7`	indirect
npm	@esbuild/darwin-x64	`0.27.7`	indirect
npm	@esbuild/freebsd-arm64	`0.27.7`	indirect
npm	@esbuild/freebsd-x64	`0.27.7`	indirect
npm	@esbuild/linux-arm	`0.27.7`	indirect
npm	@esbuild/linux-arm64	`0.27.7`	indirect
npm	@esbuild/linux-ia32	`0.27.7`	indirect
npm	@esbuild/linux-loong64	`0.27.7`	indirect
npm	@esbuild/linux-mips64el	`0.27.7`	indirect
npm	@esbuild/linux-ppc64	`0.27.7`	indirect
npm	@esbuild/linux-riscv64	`0.27.7`	indirect
npm	@esbuild/linux-s390x	`0.27.7`	indirect
npm	@esbuild/linux-x64	`0.27.7`	indirect
npm	@esbuild/netbsd-arm64	`0.27.7`	indirect
npm	@esbuild/netbsd-x64	`0.27.7`	indirect
npm	@esbuild/openbsd-arm64	`0.27.7`	indirect
npm	@esbuild/openbsd-x64	`0.27.7`	indirect
npm	@esbuild/openharmony-arm64	`0.27.7`	indirect
npm	@esbuild/sunos-x64	`0.27.7`	indirect
npm	@esbuild/win32-arm64	`0.27.7`	indirect
npm	@esbuild/win32-ia32	`0.27.7`	indirect
npm	@esbuild/win32-x64	`0.27.7`	indirect
npm	@jridgewell/gen-mapping	`0.3.13`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@jridgewell/trace-mapping	`0.3.31`	indirect
npm	@rollup/rollup-android-arm-eabi	`4.62.3`	indirect
npm	@rollup/rollup-android-arm64	`4.62.3`	indirect
npm	@rollup/rollup-darwin-arm64	`4.62.3`	indirect
npm	@rollup/rollup-darwin-x64	`4.62.3`	indirect
npm	@rollup/rollup-freebsd-arm64	`4.62.3`	indirect
npm	@rollup/rollup-freebsd-x64	`4.62.3`	indirect
npm	@rollup/rollup-linux-arm-gnueabihf	`4.62.3`	indirect
npm	@rollup/rollup-linux-arm-musleabihf	`4.62.3`	indirect
npm	@rollup/rollup-linux-arm64-gnu	`4.62.3`	indirect
npm	@rollup/rollup-linux-arm64-musl	`4.62.3`	indirect
npm	@rollup/rollup-linux-loong64-gnu	`4.62.3`	indirect
npm	@rollup/rollup-linux-loong64-musl	`4.62.3`	indirect
npm	@rollup/rollup-linux-ppc64-gnu	`4.62.3`	indirect
npm	@rollup/rollup-linux-ppc64-musl	`4.62.3`	indirect
npm	@rollup/rollup-linux-riscv64-gnu	`4.62.3`	indirect
npm	@rollup/rollup-linux-riscv64-musl	`4.62.3`	indirect
npm	@rollup/rollup-linux-s390x-gnu	`4.62.3`	indirect
npm	@rollup/rollup-linux-x64-gnu	`4.62.3`	indirect
npm	@rollup/rollup-linux-x64-musl	`4.62.3`	indirect
npm	@rollup/rollup-openbsd-x64	`4.62.3`	indirect
npm	@rollup/rollup-openharmony-arm64	`4.62.3`	indirect
npm	@rollup/rollup-win32-arm64-msvc	`4.62.3`	indirect
npm	@rollup/rollup-win32-ia32-msvc	`4.62.3`	indirect
npm	@rollup/rollup-win32-x64-gnu	`4.62.3`	indirect
npm	@rollup/rollup-win32-x64-msvc	`4.62.3`	indirect
npm	@types/chai	`5.2.3`	indirect
npm	@types/deep-eql	`4.0.2`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/node	`20.19.43`	indirect
npm	@vitest/expect	`3.2.6`	indirect
npm	@vitest/mocker	`3.2.6`	indirect
npm	@vitest/pretty-format	`3.2.6`	indirect
npm	@vitest/pretty-format	`3.2.7`	indirect
npm	@vitest/runner	`3.2.6`	indirect
npm	@vitest/snapshot	`3.2.6`	indirect
npm	@vitest/spy	`3.2.6`	indirect
npm	@vitest/utils	`3.2.6`	indirect
npm	acorn	`8.17.0`	indirect
npm	any-promise	`1.3.0`	indirect
npm	assertion-error	`2.0.1`	indirect
npm	bundle-require	`5.1.0`	indirect
npm	cac	`6.7.14`	indirect
npm	chai	`5.3.3`	indirect
npm	check-error	`2.1.3`	indirect
npm	chokidar	`4.0.3`	indirect
npm	commander	`4.1.1`	indirect
npm	confbox	`0.1.8`	indirect
npm	consola	`3.4.2`	indirect
npm	debug	`4.4.3`	indirect
npm	deep-eql	`5.0.2`	indirect
npm	es-module-lexer	`1.7.0`	indirect
npm	esbuild	`0.27.7`	indirect
npm	estree-walker	`3.0.3`	indirect
npm	expect-type	`1.4.0`	indirect
npm	fdir	`6.5.0`	indirect
npm	fix-dts-default-cjs-exports	`1.0.1`	indirect
npm	fsevents	`2.3.3`	indirect
npm	joycon	`3.1.1`	indirect
npm	js-tokens	`9.0.1`	indirect
npm	lilconfig	`3.1.3`	indirect
npm	lines-and-columns	`1.2.4`	indirect
npm	load-tsconfig	`0.2.5`	indirect
npm	loupe	`3.2.1`	indirect
npm	magic-string	`0.30.21`	indirect
npm	mlly	`1.8.2`	indirect
npm	ms	`2.1.3`	indirect
npm	mz	`2.7.0`	indirect
npm	nanoid	`3.3.16`	indirect
npm	object-assign	`4.1.1`	indirect
npm	pathe	`2.0.3`	indirect
npm	pathval	`2.0.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.5`	indirect
npm	pirates	`4.0.7`	indirect
npm	pkg-types	`1.3.1`	indirect
npm	postcss	`8.5.23`	indirect
npm	postcss-load-config	`6.0.1`	indirect
npm	prettier	`3.9.6`	indirect
npm	readdirp	`4.1.2`	indirect
npm	resolve-from	`5.0.0`	indirect
npm	rollup	`4.62.3`	indirect
npm	siginfo	`2.0.0`	indirect
npm	source-map	`0.7.6`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	stackback	`0.0.2`	indirect
npm	std-env	`3.10.0`	indirect
npm	strip-literal	`3.1.0`	indirect
npm	sucrase	`3.35.1`	indirect
npm	thenify	`3.3.1`	indirect
npm	thenify-all	`1.6.0`	indirect
npm	tinybench	`2.9.0`	indirect
npm	tinyexec	`0.3.2`	indirect
npm	tinyglobby	`0.2.17`	indirect
npm	tinypool	`1.1.1`	indirect
npm	tinyrainbow	`2.0.0`	indirect
npm	tinyspy	`4.0.4`	indirect
npm	tree-kill	`1.2.2`	indirect
npm	ts-interface-checker	`0.1.13`	indirect
npm	tsup	`8.5.1`	indirect
npm	typescript	`5.9.3`	indirect
npm	ufo	`1.6.4`	indirect
npm	undici-types	`6.21.0`	indirect
npm	vite	`7.3.6`	indirect
npm	vite-node	`3.2.4`	indirect
npm	vitest	`3.2.6`	indirect
npm	why-is-node-running	`2.3.0`	indirect

Dependency advisories 2

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

Package	Version	Relation	Severity	Advisories	Fixed in
nanoid	`3.3.16`	indirect	high	1	`5.1.6`
esbuild	`0.27.7`	indirect	low	1	`0.28.1`

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records