Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-15 05:35 UTC

hustcc / jest-canvas-mock

:last_quarter_moon: A module used to mock canvas in Jest.

JavaScriptMIT★ 312 stars⑂ 55 forkssince Dec 2017View on GitHub ↗

hustcc/jest-canvas-mock holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Community & Adoption (77/100) and lowest on AI Readiness (35/100). It was last updated 36 days ago. 2 contributors account for most of its recent work.

69
overall / 100
Good

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.

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

Ownership

hustccPersonal account
4,437 followers96 public repossince Jun 2014CN

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
npmjest-canvas-mock2.5.811,875,0202836 days agomockjestjest-mockechartscanvastestunit

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
18/36Push recencylast push 36 days ago
0.7/36Commit cadence1/52 weeks with commits
5.4/18Commit volume3 commits in the last year
3/10OpenSSF Scorecard: Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push36
active_weeks_last_year1
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 36 days ago
5.4/27Release cadencea release every ~373.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv2.5.8
releases_from_tagsno
days_since_latest_release36
mean_days_between_releases373.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?

77Good · 17% of overall
How it's scored
40.4/60Stars312 stars
14.4/25Forks55 forks
0/15Watchers2 watchers
Inputs used
forks55
stars312
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads11,875,020 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesjest-canvas-mock
dependents
ecosystemsnpm
total_downloads
monthly_downloads11,875,020
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?

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.2/22.5Commit distributiontop contributor authored 37% of commits
13.5/13.5Contributor breadth25 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled25
top_contributor_share0.367
How it's scored
31/42Issue resolution74% of issues closed
26.4/30PR acceptance52/59 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 21/28 approved changesets -- score normalized to 7
Inputs used
merged_prs52
open_issues18
closed_issues51
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.739
closed_unmerged_prs7
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
25/25Owner reach4,437 followers of hustcc
25/25Track record96 public repos, account ~12 yr old
Inputs used
followers4,437
owner_typeUser
is_verified
owner_loginhustcc
public_repos96
account_age_days4,447
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 36 days ago
20/20Version history28 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjest-canvas-mock
ecosystemsnpm
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests3 out of 27 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/hustcc/jest-canvas-mock
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsjest, jest-test, canvas, mock, ci, echarts
has_wikino
homepagehttps://github.com/hustcc/jest-canvas-mock
docs_sitehttps://github.com/hustcc/jest-canvas-mock
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests3 out of 27 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 21/28 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:jest-canvas-mock@2.5.8 runtime dependency closure — what installing the published package pulls in — 3 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history81 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.81
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/98 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes56,638
source_files_sampled98
oversized_source_files0

Key facts

312GitHub stars
25contributors
3commits, last 12 months
36days since last push
8releases
2bus factor
18open 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 ★ / 55 ⇿
0Stars
55Forks
7Releases

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.

0102030403922018-012022-042026-07
Major 0Minor 5Patch 2

Each point covers 8 days.

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-15 05:35 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
1CI-Tests3 out of 27 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 21/28 approved changesets -- score normalized to 7
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmcssfontparser^1.2.1package.json
npmmoo-color^1.0.2package.json
All dependencies 15

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

RegistryPackageVersionRelation
npmcssfontparser^1.2.1direct
npmmoo-color^1.0.2direct
npm@antv/g2plot^2.3.11indirect
npm@babel/cli^7.8.4indirect
npm@babel/core^7.9.0indirect
npm@babel/plugin-proposal-class-properties^7.8.3indirect
npm@babel/preset-env^7.9.5indirect
npm@commitlint/cli^8.3.5indirect
npm@commitlint/config-angular^8.3.4indirect
npmbabel-jest^25.3.0indirect
npmbabel-plugin-version^0.2.3indirect
npmcoveralls^3.0.11indirect
npmhusky^4.2.5indirect
npmjest^25.3.0indirect
npmprettier^2.0.4indirect
Dependency advisories 0

Installing npm:jest-canvas-mock@2.5.8 pulls in 3 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.