Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 13:38 UTC

dfederm / karma-jasmine-html-reporter

A Karma plugin. Dynamically displays tests results at debug.html page

JavaScriptMIT★ 38 stars⑂ 32 forkssince Mar 2018View on GitHub ↗

dfederm/karma-jasmine-html-reporter holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (65/100) and lowest on AI Readiness (34/100). It was last updated 10 days ago. 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 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02).

Ownership

David FedermanPersonal account

89 followers53 public repossince Jan 2014@Microsoft

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	karma-jasmine-html-reporter	2.3.0	8,433,041	27	30 days ago	karma-plugin karma-reporter html

Metrics by category

Vitality

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

58Moderate · 21% of overall

Development activity

40Weak

How it's scored

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

Inputs used

commits_last_year	5
human_commit_share	0.983
days_since_last_push	10
active_weeks_last_year	2

Release discipline

84Excellent

How it's scored

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

Inputs used

releases_count	19
latest_release_tag	v2.3.0
releases_from_tags	no
days_since_latest_release	30
mean_days_between_releases	269.9

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

38Weak

How it's scored

25.4/60	Stars — 38 stars
12.4/25	Forks — 32 forks
0/15	Watchers — 1 watchers

Inputs used

forks	32
stars	38
watchers	1
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	2
has_contributing	yes
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 8,433,041 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	karma-jasmine-html-reporter
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	8,433,041
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?

58Moderate · 23% of overall

Maintainer resilience (bus factor)

30At Risk

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	6
top_contributor_share	0.574

Issue & PR responsiveness

57Moderate

How it's scored

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

Inputs used

merged_prs	10
open_issues	0
closed_issues	48
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	38
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

61Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
14.1/25	Owner reach — 89 followers of dfederm
24.6/25	Track record — 53 public repos, account ~12 yr old

Inputs used

followers	89
owner_type	User
is_verified	—
owner_login	dfederm
public_repos	53
account_age_days	4,624

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 30 days ago
20/20	Version history — 27 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	karma-jasmine-html-reporter
ecosystems	npm
any_deprecated	no
min_days_since_publish	30

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall

Engineering practices

52Moderate

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

50Moderate

How it's scored

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

Inputs used

topics	—
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?

53Moderate · 16% of overall

Security posture

41Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
2.2/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5	CI-Tests — 2 out of 9 merged PRs checked by a CI test -- score normalized to 2
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5	Code-Review — Found 5/29 approved changesets -- score normalized to 1
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
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
2.2/7.5	Maintained — 3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
5/5	Packaging — packaging workflow detected
1/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
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 — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 25 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	4.1

Excluded from scoring (no data or not applicable): Signed-Releases. 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	25
affected_packages	12
assessed_packages	151
unassessed_packages	0
affected_by_severity	critical 1, high 8, moderate 2, 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 151 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.

34At Risk · 4% of overall

Agent context & guidance

14Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.254
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

42Weak

How it's scored

0/18	One-command bootstrap
22/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 60
8/8	Automated maintenance — 1 of the last 60 commits are automated dependency updates
2/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2

Inputs used

has_nix	no
has_tests	yes
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.017

Code legibility for models

55Moderate

How it's scored

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

Inputs used

primary_language	JavaScript
largest_source_bytes	6,503
source_files_sampled	5
oversized_source_files	0

Key facts

38GitHub stars

6contributors

5commits, last 12 months

10days since last push

19releases

1bus factor

0open 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 ★ / 32 ⇿

0Stars

32Forks

18Releases

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 2Minor 9Patch 7

Each point covers 8 days.

OpenSSF Scorecard 4.1 / 10

4.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-09-18 13:38 UTC

10	Binary-Artifacts	no binaries found in the repo
3	Branch-Protection	branch protection is not maximal on development and all release branches
2	CI-Tests	2 out of 9 merged PRs checked by a CI test -- score normalized to 2
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
1	Code-Review	Found 5/29 approved changesets -- score normalized to 1
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
3	Maintained	3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
10	Packaging	packaging workflow detected
2	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 2
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
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	25 existing vulnerabilities detected

All dependencies 151

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

Registry	Package	Version	Relation
npm	@colors/colors	`1.5.0`	indirect
npm	@socket.io/component-emitter	`3.1.2`	indirect
npm	@types/cors	`2.8.19`	indirect
npm	@types/node	`25.0.10`	indirect
npm	accepts	`1.3.8`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	base64id	`2.0.0`	indirect
npm	binary-extensions	`2.3.0`	indirect
npm	body-parser	`1.20.4`	indirect
npm	brace-expansion	`1.1.12`	indirect
npm	braces	`3.0.3`	indirect
npm	bytes	`3.1.2`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	chokidar	`3.6.0`	indirect
npm	cliui	`7.0.4`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	concat-map	`0.0.1`	indirect
npm	connect	`3.7.0`	indirect
npm	content-type	`1.0.5`	indirect
npm	cookie	`0.7.2`	indirect
npm	cors	`2.8.6`	indirect
npm	custom-event	`1.0.1`	indirect
npm	date-format	`4.0.14`	indirect
npm	debug	`2.6.9`	indirect
npm	debug	`4.4.3`	indirect
npm	depd	`2.0.0`	indirect
npm	destroy	`1.2.0`	indirect
npm	di	`0.0.1`	indirect
npm	dom-serialize	`2.2.1`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	ee-first	`1.1.1`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	encodeurl	`1.0.2`	indirect
npm	engine.io	`6.6.5`	indirect
npm	engine.io-parser	`5.2.3`	indirect
npm	ent	`2.2.2`	indirect
npm	es-define-property	`1.0.1`	indirect
npm	es-errors	`1.3.0`	indirect
npm	es-object-atoms	`1.1.1`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-html	`1.0.3`	indirect
npm	eventemitter3	`4.0.7`	indirect
npm	extend	`3.0.2`	indirect
npm	fill-range	`7.1.1`	indirect
npm	finalhandler	`1.1.2`	indirect
npm	flatted	`3.3.3`	indirect
npm	follow-redirects	`1.15.11`	indirect
npm	fs-extra	`8.1.0`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	glob	`7.2.3`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	gopd	`1.2.0`	indirect
npm	graceful-fs	`4.2.11`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hasown	`2.0.2`	indirect
npm	http-errors	`2.0.1`	indirect
npm	http-proxy	`1.18.1`	indirect
npm	iconv-lite	`0.4.24`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-regex	`1.2.1`	indirect
npm	isbinaryfile	`4.0.10`	indirect
npm	isexe	`2.0.0`	indirect
npm	jasmine-core	`4.6.1`	indirect
npm	jasmine-core	`7.0.1`	indirect
npm	jsonfile	`4.0.0`	indirect
npm	karma	`6.4.4`	indirect
npm	karma-chrome-launcher	`3.2.0`	indirect
npm	karma-jasmine	`5.1.0`	indirect
npm	lodash	`4.17.23`	indirect
npm	log4js	`6.9.1`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	media-typer	`0.3.0`	indirect
npm	mime	`2.6.0`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	minimatch	`3.1.2`	indirect
npm	minimist	`1.2.8`	indirect
npm	mkdirp	`0.5.6`	indirect
npm	ms	`2.0.0`	indirect
npm	ms	`2.1.3`	indirect
npm	negotiator	`0.6.3`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	object-assign	`4.1.1`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	on-finished	`2.3.0`	indirect
npm	on-finished	`2.4.1`	indirect
npm	once	`1.4.0`	indirect
npm	parseurl	`1.3.3`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	punycode	`1.4.1`	indirect
npm	qjobs	`1.2.0`	indirect
npm	qs	`6.14.1`	indirect
npm	range-parser	`1.2.1`	indirect
npm	raw-body	`2.5.3`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	requires-port	`1.0.0`	indirect
npm	rfdc	`1.4.1`	indirect
npm	rimraf	`3.0.2`	indirect
npm	safe-regex-test	`1.1.0`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	setprototypeof	`1.2.0`	indirect
npm	side-channel	`1.1.0`	indirect
npm	side-channel-list	`1.0.0`	indirect
npm	side-channel-map	`1.0.1`	indirect
npm	side-channel-weakmap	`1.0.2`	indirect
npm	socket.io	`4.8.3`	indirect
npm	socket.io-adapter	`2.5.6`	indirect
npm	socket.io-parser	`4.2.5`	indirect
npm	source-map	`0.6.1`	indirect
npm	statuses	`1.5.0`	indirect
npm	statuses	`2.0.2`	indirect
npm	streamroller	`3.1.5`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	tmp	`0.2.5`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	toidentifier	`1.0.1`	indirect
npm	type-is	`1.6.18`	indirect
npm	ua-parser-js	`0.7.41`	indirect
npm	undici-types	`7.16.0`	indirect
npm	universalify	`0.1.2`	indirect
npm	unpipe	`1.0.0`	indirect
npm	utils-merge	`1.0.1`	indirect
npm	vary	`1.1.2`	indirect
npm	void-elements	`2.0.1`	indirect
npm	which	`1.3.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	ws	`8.18.3`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs-parser	`20.2.9`	indirect

Dependency advisories 12

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

Package	Version	Relation	Severity	Advisories	Fixed in
flatted	`3.3.3`	indirect	critical	2	`3.4.2`
brace-expansion	`1.1.12`	indirect	high	4	`5.0.9`
engine.io	`6.6.5`	indirect	high	2	`6.6.7`
lodash	`4.17.23`	indirect	high	2	`4.18.0`
minimatch	`3.1.2`	indirect	high	3	`10.2.3`
picomatch	`2.3.1`	indirect	high	2	`4.0.4`
socket.io-parser	`4.2.5`	indirect	high	2	`4.2.7`
tmp	`0.2.5`	indirect	high	1	`0.2.6`
ws	`8.18.3`	indirect	high	2	`8.21.0`
follow-redirects	`1.15.11`	indirect	moderate	1	`1.16.0`
qs	`6.14.1`	indirect	moderate	3	`6.16.0`
body-parser	`1.20.4`	indirect	low	1	`2.3.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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records