Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 18:11 UTC

dtabuenc / karma-html-reporter

Karma Html Reporter Plugin

JavaScript · HTMLMIT★ 45 stars⑂ 28 forkssince Oct 2013View on GitHub ↗

dtabuenc/karma-html-reporter holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (61/100) and lowest on Vitality (20/100). It was last updated 1282 days ago. A single contributor accounts for most of its recent work.

19
overall / 100
Critical

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.

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

Ownership

Daniel TabuencaPersonal account
16 followers25 public repossince Jan 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmkarma-html-reporter0.2.752,608104030 days agokarma-pluginkarma-reporterhtml

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
0/36Push recency — last push 1,282 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.962
days_since_last_push1,282
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 4 version tags (no GitHub releases)
0/36Release recency — latest release 4,602 days ago
27/27Release cadence — a release every ~9.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tagv0.2.3
releases_from_tagsyes
days_since_latest_release4,602
mean_days_between_releases9.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?

61Moderate · 17% of overall
How it's scored
26.7/60Stars — 45 stars
11.9/25Forks — 28 forks
2.7/15Watchers — 4 watchers
Inputs used
forks28
stars45
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
62.9/80Monthly downloads — 52,608 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageskarma-html-reporter
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads52,608
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?

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.4/22.5Commit distribution — top contributor authored 63% of commits
13.5/13.5Contributor breadth — 11 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.628
How it's scored
24/42Issue resolution — 57% of issues closed
19.1/30PR acceptance — 14/22 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 8/19 approved changesets -- score normalized to 4
Inputs used
merged_prs14
open_issues12
closed_issues16
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.571
closed_unmerged_prs8
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.8/25Owner reach — 16 followers of dtabuenc
22.3/25Track record — 25 public repos, account ~17 yr old
Inputs used
followers16
owner_typeUser
is_verified—
owner_logindtabuenc
public_repos25
account_age_days6,494
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 4,030 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageskarma-html-reporter
ecosystemsnpm
any_deprecatedno
min_days_since_publish4,030

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 10 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
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?

37Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 8/19 approved changesets -- score normalized to 4
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 32 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.9
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
9.5/35Direct dependencies free of known advisories — 1 affected: lodash 2.2.1 (critical 9.1)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
32.6/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 3,006 days ago
Inputs used
sourceosv
advisories5
affected_packages1
assessed_packages2
unassessed_packages0
affected_by_severitycritical 1
direct_affected_packages1
Matched the npm:karma-html-reporter@0.2.7 runtime dependency closure — what installing the published package pulls in — 2 packages. 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.

31At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
33.5/40Legible commit history — 32 of 51 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.627
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 53
8/8Automated maintenance — 2 of the last 53 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.038
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/1 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes8,659
source_files_sampled1
oversized_source_files0

Key facts

45GitHub stars
11contributors
0commits, last 12 months
1,282days since last push
4releases
1bus factor
12open 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 ★ / 28 ⇿
0Stars
28Forks
4Releases

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.

0510152025302722013-122018-062022-11
Major 0Minor 0Patch 4

Each point covers 9 days.

OpenSSF Scorecard 2.9 / 10
2.9aggregate

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-10-18 18:11 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 8/19 approved changesets -- score normalized to 4
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities32 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmlodash^4.17.11package.json
npmmu2~0.5.19package.json
All dependencies 100

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

RegistryPackageVersionRelation
npmlodash4.17.21direct
npmmu20.5.21direct
npmabbrev1.1.1indirect
npmansi-styles3.2.1indirect
npmargparse1.0.10indirect
npmarray-find-index1.0.2indirect
npmasync1.5.2indirect
npmbalanced-match1.0.0indirect
npmbrace-expansion1.1.11indirect
npmbuiltin-modules1.1.1indirect
npmcamelcase2.1.1indirect
npmcamelcase-keys2.1.0indirect
npmchalk2.4.1indirect
npmcoffeescript1.10.0indirect
npmcolor-convert1.9.3indirect
npmcolor-name1.1.3indirect
npmcolors1.1.2indirect
npmconcat-map0.0.1indirect
npmcurrently-unhandled0.4.1indirect
npmdateformat1.0.12indirect
npmdecamelize1.2.0indirect
npmerror-ex1.3.2indirect
npmescape-string-regexp1.0.5indirect
npmesprima2.7.3indirect
npmeventemitter20.4.14indirect
npmexit0.1.2indirect
npmfind-up1.1.2indirect
npmfindup-sync0.3.0indirect
npmfs.realpath1.0.0indirect
npmget-stdin4.0.1indirect
npmgetobject0.1.0indirect
npmglob5.0.15indirect
npmglob7.0.6indirect
npmgraceful-fs4.1.11indirect
npmgrunt1.0.3indirect
npmgrunt-auto-release0.0.7indirect
npmgrunt-bump0.8.0indirect
npmgrunt-cli1.2.0indirect
npmgrunt-known-options1.1.1indirect
npmgrunt-legacy-log2.0.0indirect
npmgrunt-legacy-log-utils2.0.1indirect
npmgrunt-legacy-util1.1.1indirect
npmgrunt-npm0.0.2indirect
npmhas-flag3.0.0indirect
npmhooker0.2.3indirect
npmhosted-git-info2.7.1indirect
npmiconv-lite0.4.24indirect
npmindent-string2.1.0indirect
npminflight1.0.6indirect
npminherits2.0.3indirect
npmis-arrayish0.2.1indirect
npmis-builtin-module1.0.0indirect
npmis-finite1.0.2indirect
npmis-utf80.2.1indirect
npmisexe2.0.0indirect
npmjs-yaml3.5.5indirect
npmload-json-file1.1.0indirect
npmloud-rejection1.6.0indirect
npmmap-obj1.0.1indirect
npmmeow3.7.0indirect
npmminimatch3.0.4indirect
npmminimist0.0.8indirect
npmminimist1.2.0indirect
npmmkdirp0.5.1indirect
npmnopt3.0.6indirect
npmnormalize-package-data2.4.0indirect
npmnumber-is-nan1.0.1indirect
npmobject-assign4.1.1indirect
npmonce1.4.0indirect
npmparse-json2.2.0indirect
npmpath-exists2.1.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-type1.1.0indirect
npmpify2.3.0indirect
npmpinkie2.0.4indirect
npmpinkie-promise2.0.1indirect
npmread-pkg1.1.0indirect
npmread-pkg-up1.0.1indirect
npmredent1.0.0indirect
npmrepeating2.0.1indirect
npmresolve1.1.7indirect
npmrimraf2.6.2indirect
npmsafer-buffer2.1.2indirect
npmsemver5.6.0indirect
npmsignal-exit3.0.2indirect
npmspdx-correct3.0.2indirect
npmspdx-exceptions2.2.0indirect
npmspdx-expression-parse3.0.0indirect
npmspdx-license-ids3.0.1indirect
npmsprintf-js1.0.3indirect
npmsprintf-js1.1.1indirect
npmstrip-bom2.0.0indirect
npmstrip-indent1.0.1indirect
npmsupports-color5.5.0indirect
npmtrim-newlines1.0.0indirect
npmunderscore.string3.3.5indirect
npmutil-deprecate1.0.2indirect
npmvalidate-npm-package-license3.0.4indirect
npmwhich1.3.1indirect
npmwrappy1.0.2indirect
Dependency advisories 1

Installing npm:karma-html-reporter@0.2.7 pulls in 2 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
lodash2.2.1directcritical54.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.

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 statistics — npm.