Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 19:19 UTC

GoogleChromeLabs / jsvu

JavaScript (engine) Version Updater

JavaScriptApache-2.0★ 2,031 stars⑂ 98 forkssince Nov 2017View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

GoogleChromeLabs/jsvu holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (73/100) and lowest on AI Readiness (17/100). It was last updated 36 days ago. A single contributor accounts for most of its recent work.

57
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.

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

Ownership

GoogleChromeLabsOrganization
3,099 followers257 public repossince Sep 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmjsvu3.0.513,9597436 days agojavascript-enginesinstallerjavascriptcorejscspidermonkeyv8

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
18/36Push recencylast push 36 days ago
2.1/36Commit cadence3/52 weeks with commits
9.7/18Commit volume11 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year11
human_commit_share1
days_since_last_push36
active_weeks_last_year3
How it's scored
16.2/27Ships releases74 version tags (no GitHub releases)
36/36Release recencylatest release 36 days ago
19.8/27Release cadencea release every ~68.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count74
latest_release_tagv3.0.5
releases_from_tagsyes
days_since_latest_release36
mean_days_between_releases68.7
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?

73Good · 17% of overall
How it's scored
53.7/60Stars2,031 stars
16.6/25Forks98 forks
9.1/15Watchers45 watchers
Inputs used
forks98
stars2,031
watchers45
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
55.3/80Monthly downloads13,959 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesjsvu
dependents
ecosystemsnpm
total_downloads
monthly_downloads13,959
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?

69Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.7/22.5Commit distributiontop contributor authored 79% of commits
13.5/13.5Contributor breadth31 contributors
10/10OpenSSF Scorecard: Contributorsproject has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled31
top_contributor_share0.791
How it's scored
30.7/42Issue resolution73% of issues closed
27/30PR acceptance54/60 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 11/30 approved changesets -- score normalized to 3
Inputs used
merged_prs54
open_issues29
closed_issues79
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.731
closed_unmerged_prs6
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
30/30Ownership backingorganization-owned
0/20Verified domain
25/25Owner reach3,099 followers of GoogleChromeLabs
25/25Track record257 public repos, account ~8 yr old
Inputs used
followers3,099
owner_typeOrganization
is_verifiedno
owner_loginGoogleChromeLabs
public_repos257
account_age_days3,276

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests3 out of 12 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://mths.be/jsvu
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsjavascript, javascript-engine, installer, installer-script
has_wikino
homepagehttps://mths.be/jsvu
docs_sitehttps://mths.be/jsvu
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.5/2.5CI-Tests3 out of 12 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 11/30 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 18 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
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
7.8/35Direct dependencies free of known advisories3 affected: extract-zip 1.7.0 (high 8.1), tar 4.4.19 (high 8.8), got 9.6.0 (moderate 5.3)
8.4/25Indirect dependencies free of known advisories2 affected: cross-spawn 5.1.0 (high 7.5), tmp 0.0.33 (high 7.5)
23.2/40No advisories left outstanding4 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,538 days ago
Inputs used
sourceosv
advisories18
affected_packages5
assessed_packages181
unassessed_packages0
affected_by_severityhigh 4, moderate 1
direct_affected_packages3
Matched the npm:jsvu@3.0.5 runtime dependency closure — what installing the published package pulls in — 181 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.

17Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
20.3/40Legible commit history38 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.38
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
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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_testsno
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/62 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes5,696
source_files_sampled62
oversized_source_files0

Key facts

2,031GitHub stars
31contributors
11commits, last 12 months
36days since last push
74releases
1bus factor
29open 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 ★ / 98 ⇿
0Stars
98Forks
72Releases

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.

0204060801009652017-122022-042026-08
Major 2Minor 19Patch 51

Each point covers 8 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-04 19:19 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests3 out of 12 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 11/30 approved changesets -- score normalized to 3
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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 13
RegistryPackageVersion constraintManifest
npmchalk^2.4.2package.json
npmexeca^2.0.4package.json
npmextract-zip^1.6.7package.json
npmfs-extra^8.1.0package.json
npmglob^7.1.4package.json
npmgot^9.6.0package.json
npminquirer^6.5.1package.json
npmprogress^2.0.3package.json
npmtar^4.4.10package.json
npmtempy^0.5.0package.json
npmtildify^2.0.0package.json
npmuntildify^4.0.0package.json
npmupdate-notifier^3.0.1package.json
All dependencies 13

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

RegistryPackageVersionRelation
npmchalk^2.4.2direct
npmexeca^2.0.4direct
npmextract-zip^1.6.7direct
npmfs-extra^8.1.0direct
npmglob^7.1.4direct
npmgot^9.6.0direct
npminquirer^6.5.1direct
npmprogress^2.0.3direct
npmtar^4.4.10direct
npmtempy^0.5.0direct
npmtildify^2.0.0direct
npmuntildify^4.0.0direct
npmupdate-notifier^3.0.1direct
Dependency advisories 5

Installing npm:jsvu@3.0.5 pulls in 181 packages, direct and transitive: 5 carry known advisories, of which 3 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
extract-zip1.7.0directhigh1
tar4.4.19directhigh137.5.21
cross-spawn5.1.0indirecthigh17.0.5
tmp0.0.33indirecthigh20.2.6
got9.6.0directmoderate112.1.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 statisticsnpm.