Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 06:13 UTC

vitejs / launch-editor

Open file in editor from Node.js.

JavaScriptMIT★ 720 stars⑂ 99 forkssince Jan 2018View on GitHub ↗

vitejs/launch-editor holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (76/100) and lowest on AI Readiness (47/100). It was last updated 7 days ago. 2 contributors account for most of its recent work.

83
overall / 100
Excellent

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.

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

Ownership

ViteOrganization · verified domain
4,841 followers32 public repossince May 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmlaunch-editor2.14.2126,075,0002415 days agoeditorlaunch
npmlaunch-editor-middleware2.14.22,955,1472515 days agoeditorexpressmiddleware

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
6.2/36Commit cadence — 9/52 weeks with commits
15.3/18Commit volume — 50 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year50
human_commit_share0.84
days_since_last_push7
active_weeks_last_year9
How it's scored
16.2/27Ships releases — 26 version tags (no GitHub releases)
36/36Release recency — latest release 15 days ago
19.8/27Release cadence — a release every ~66.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tagv2.14.2
releases_from_tagsyes
days_since_latest_release15
mean_days_between_releases66.2
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?

75Good · 17% of overall
How it's scored
46.3/60Stars — 720 stars
16.6/25Forks — 99 forks
3.9/15Watchers — 6 watchers
Inputs used
forks99
stars720
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 129,030,147 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslaunch-editor, launch-editor-middleware
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads129,030,147
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.2/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 32 contributors
10/10OpenSSF Scorecard: Contributors — project has 10 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled32
top_contributor_share0.324
How it's scored
28.6/42Issue resolution — 68% of issues closed
21.5/30PR acceptance — 71/99 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/17 approved changesets -- score normalized to 0
Inputs used
merged_prs71
open_issues15
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.681
closed_unmerged_prs28
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 4,841 followers of vitejs
23.1/25Track record — 32 public repos, account ~6 yr old
Inputs used
followers4,841
owner_typeOrganization
is_verifiedyes
owner_loginvitejs
public_repos32
account_age_days2,345

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 15 days ago
20/20Version history — 25 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslaunch-editor, launch-editor-middleware
ecosystemsnpm
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
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?

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/17 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 10 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 65 of 84 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.774
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
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 16 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.16
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/18 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,687
source_files_sampled18
oversized_source_files0

Key facts

720GitHub stars
32contributors
50commits, last 12 months
7days since last push
26releases
2bus factor
15open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OSV advisory lookup failed: [Errno 101] Network is unreachable

More detail

Star and fork history 0 ★ / 99 ⇿
0Stars
99Forks
26Releases

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.

0204060801009742018-012022-052026-10
Major 2Minor 14Patch 10

Each point covers 9 days.

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-21 06:12 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/17 approved changesets -- score normalized to 0
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmlaunch-editorworkspace:^packages/launch-editor-middleware/package.json
npmpicocolors^1.1.1packages/launch-editor/package.json
npmshell-quote^1.10.0packages/launch-editor/package.json
All dependencies 85

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

RegistryPackageVersionRelation
npmpicocolors1.1.1direct
npmpicocolors^1.1.1direct
npmshell-quote1.10.0direct
npmshell-quote^1.10.0direct
npm@oxfmt/binding-android-arm-eabi0.65.0indirect
npm@oxfmt/binding-android-arm640.65.0indirect
npm@oxfmt/binding-darwin-arm640.65.0indirect
npm@oxfmt/binding-darwin-x640.65.0indirect
npm@oxfmt/binding-freebsd-x640.65.0indirect
npm@oxfmt/binding-linux-arm-gnueabihf0.65.0indirect
npm@oxfmt/binding-linux-arm-musleabihf0.65.0indirect
npm@oxfmt/binding-linux-arm64-gnu0.65.0indirect
npm@oxfmt/binding-linux-arm64-musl0.65.0indirect
npm@oxfmt/binding-linux-ppc64-gnu0.65.0indirect
npm@oxfmt/binding-linux-riscv64-gnu0.65.0indirect
npm@oxfmt/binding-linux-riscv64-musl0.65.0indirect
npm@oxfmt/binding-linux-s390x-gnu0.65.0indirect
npm@oxfmt/binding-linux-x64-gnu0.65.0indirect
npm@oxfmt/binding-linux-x64-musl0.65.0indirect
npm@oxfmt/binding-openharmony-arm640.65.0indirect
npm@oxfmt/binding-win32-arm64-msvc0.65.0indirect
npm@oxfmt/binding-win32-ia32-msvc0.65.0indirect
npm@oxfmt/binding-win32-x64-msvc0.65.0indirect
npm@oxlint/binding-android-arm-eabi1.80.0indirect
npm@oxlint/binding-android-arm641.80.0indirect
npm@oxlint/binding-darwin-arm641.80.0indirect
npm@oxlint/binding-darwin-x641.80.0indirect
npm@oxlint/binding-freebsd-x641.80.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.80.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.80.0indirect
npm@oxlint/binding-linux-arm64-gnu1.80.0indirect
npm@oxlint/binding-linux-arm64-musl1.80.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.80.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.80.0indirect
npm@oxlint/binding-linux-riscv64-musl1.80.0indirect
npm@oxlint/binding-linux-s390x-gnu1.80.0indirect
npm@oxlint/binding-linux-x64-gnu1.80.0indirect
npm@oxlint/binding-linux-x64-musl1.80.0indirect
npm@oxlint/binding-openharmony-arm641.80.0indirect
npm@oxlint/binding-win32-arm64-msvc1.80.0indirect
npm@oxlint/binding-win32-ia32-msvc1.80.0indirect
npm@oxlint/binding-win32-x64-msvc1.80.0indirect
npm@quansync/fs1.0.0indirect
npmargs-tokenizer0.3.0indirect
npmbumpp11.1.0indirect
npmcac7.0.0indirect
npmci-info1.6.0indirect
npmcross-spawn5.1.0indirect
npmdefu6.1.4indirect
npmexeca0.8.0indirect
npmfdir6.5.0indirect
npmget-stream3.0.0indirect
npmis-ci1.2.1indirect
npmis-stream1.1.0indirect
npmisexe2.0.0indirect
npmjiti2.6.1indirect
npmjsonc-parser3.3.1indirect
npmlint-staged17.4.1indirect
npmlru-cache4.1.5indirect
npmnormalize-path1.0.0indirect
npmnpm-run-path2.0.2indirect
npmoxfmt0.65.0indirect
npmoxlint1.80.0indirect
npmp-finally1.0.0indirect
npmpackage-manager-detector1.6.0indirect
npmpath-key2.0.1indirect
npmpicomatch4.0.7indirect
npmpseudomap1.0.2indirect
npmquansync1.0.0indirect
npmsemver7.7.4indirect
npmshebang-command1.2.0indirect
npmshebang-regex1.0.0indirect
npmsignal-exit3.0.7indirect
npmstring-argv0.3.2indirect
npmstrip-eof1.0.0indirect
npmstrip-indent2.0.0indirect
npmtinyexec1.3.0indirect
npmtinyglobby0.2.16indirect
npmtinypool2.1.0indirect
npmunconfig7.5.0indirect
npmunconfig-core7.5.0indirect
npmwhich1.3.1indirect
npmyallist2.1.2indirect
npmyaml2.9.0indirect
npmyorkie2.0.0indirect
Dependency advisories not assessed

Advisory matching could not run for this report: OSV advisory lookup failed: [Errno 101] Network is unreachable

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.