Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-26 23:27 UTC

denoland / deno-vite-plugin

Vite plugin to enable Deno resolution inside vite.

TypeScriptMIT★ 116 stars⑂ 21 forkssince Sep 2024View on GitHub ↗

denoland/deno-vite-plugin holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (71/100) and lowest on Security (50/100). It was last updated 30 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

DenoOrganization · verified domain

6,013 followers233 public repossince Aug 2018

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	@deno/vite-plugin	2.0.3	65,744	13	30 days ago	deno vite plugin

Metrics by category

Vitality

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

64Moderate · 21% of overall

Development activity

45Weak

How it's scored

28.8/36	Push recency — last push 30 days ago
2.8/36	Commit cadence — 4/52 weeks with commits
10.6/18	Commit volume — 14 commits in the last year
3/10	OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3

Inputs used

commits_last_year	14
human_commit_share	1
days_since_last_push	30
active_weeks_last_year	4

Release discipline

92Excellent

How it's scored

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

Inputs used

releases_count	15
latest_release_tag	2.0.3
releases_from_tags	no
days_since_latest_release	30
mean_days_between_releases	67.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?

56Moderate · 17% of overall

Popularity & adoption

47Weak

How it's scored

33.4/60	Stars — 116 stars
10.8/25	Forks — 21 forks
2.7/15	Watchers — 4 watchers

Inputs used

forks	21
stars	116
watchers	4
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/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	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

80Excellent

How it's scored

64.2/80	Monthly downloads — 65,744 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@deno/vite-plugin
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	65,744
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?

71Good · 23% of overall

Maintainer resilience (bus factor)

39Weak

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	8
top_contributor_share	0.591

Issue & PR responsiveness

59Moderate

How it's scored

28.6/42	Issue resolution — 68% of issues closed
26.3/30	PR acceptance — 43/49 decided PRs merged
0/13	Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
4.5/15	OpenSSF Scorecard: Code-Review — Found 9/30 approved changesets -- score normalized to 3

Inputs used

merged_prs	43
open_issues	16
closed_issues	34
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	1
issue_closed_ratio	0.68
closed_unmerged_prs	6
first_time_authors_30d	1
first_time_prs_merged_30d	0
first_time_prs_decided_30d	1

Ownership & stewardship

100Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
25/25	Owner reach — 6,013 followers of denoland
25/25	Track record — 233 public repos, account ~8 yr old

Inputs used

followers	6,013
owner_type	Organization
is_verified	yes
owner_login	denoland
public_repos	233
account_age_days	2,946

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 — 13 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	@deno/vite-plugin
ecosystems	npm
any_deprecated	no
min_days_since_publish	30

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall

Engineering practices

58Moderate

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
10/20	OpenSSF Scorecard: CI-Tests — 15 out of 30 merged PRs checked by a CI test -- score normalized to 5

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?

50Moderate · 16% of overall

Security posture

38Weak

How it's scored

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

Inputs used

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

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	15
affected_packages	4
assessed_packages	108
unassessed_packages	0
affected_by_severity	high 4
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 108 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.

57Moderate · 4% of overall

Agent context & guidance

40Weak

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.977
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

54Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — lockfile
10/10	Demonstrated agent practice — 3 of the last 44 commits agent-authored or agent-credited
0/8	Automated maintenance — no automated dependency updates observed
1/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	tsconfig.json
agent_commit_share	0.068
toolchain_manifests	—
dependency_bot_commit_share	0

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
55/55	Manageable file sizes — 0/26 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	11,070
source_files_sampled	26
oversized_source_files	0

Key facts

116GitHub stars

8contributors

14commits, last 12 months

30days since last push

15releases

1bus factor

16open 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 ★ / 21 ⇿

0Stars

21Forks

6Releases

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 0Minor 0Patch 6

Each point covers 2 days.

OpenSSF Scorecard 3.8 / 10

3.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-26 23:26 UTC

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

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	@deno/loader	`npm:@jsr/deno__loader@^0.5.0`	package.json
npm	@std/jsonc	`npm:@jsr/std__jsonc@^1`	package.json

All dependencies 108

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

Registry	Package	Version	Relation
npm	@cspotcode/source-map-support	`0.8.1`	indirect
npm	@emnapi/core	`1.9.1`	indirect
npm	@emnapi/runtime	`1.9.1`	indirect
npm	@emnapi/wasi-threads	`1.2.0`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@jridgewell/trace-mapping	`0.3.9`	indirect
npm	@jsr/deno__loader	`0.5.0`	indirect
npm	@jsr/std__bytes	`1.0.6`	indirect
npm	@jsr/std__json	`1.0.3`	indirect
npm	@jsr/std__jsonc	`1.0.2`	indirect
npm	@jsr/std__streams	`1.0.17`	indirect
npm	@napi-rs/wasm-runtime	`1.1.2`	indirect
npm	@oxc-project/types	`0.122.0`	indirect
npm	@rolldown/binding-android-arm64	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-darwin-arm64	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-darwin-x64	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-freebsd-x64	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-arm-gnueabihf	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-arm64-gnu	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-arm64-musl	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-ppc64-gnu	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-s390x-gnu	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-x64-gnu	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-linux-x64-musl	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-openharmony-arm64	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-wasm32-wasi	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-win32-arm64-msvc	`1.0.0-rc.12`	indirect
npm	@rolldown/binding-win32-x64-msvc	`1.0.0-rc.12`	indirect
npm	@rolldown/pluginutils	`1.0.0-rc.12`	indirect
npm	@standard-schema/spec	`1.1.0`	indirect
npm	@tsconfig/node10	`1.0.12`	indirect
npm	@tsconfig/node12	`1.0.11`	indirect
npm	@tsconfig/node14	`1.0.3`	indirect
npm	@tsconfig/node16	`1.0.4`	indirect
npm	@tybys/wasm-util	`0.10.1`	indirect
npm	@types/chai	`5.2.3`	indirect
npm	@types/deep-eql	`4.0.2`	indirect
npm	@types/estree	`1.0.8`	indirect
npm	@types/node	`22.19.15`	indirect
npm	@vitest/expect	`4.1.2`	indirect
npm	@vitest/mocker	`4.1.2`	indirect
npm	@vitest/pretty-format	`4.1.2`	indirect
npm	@vitest/runner	`4.1.2`	indirect
npm	@vitest/snapshot	`4.1.2`	indirect
npm	@vitest/spy	`4.1.2`	indirect
npm	@vitest/utils	`4.1.2`	indirect
npm	acorn	`8.16.0`	indirect
npm	acorn-walk	`8.3.5`	indirect
npm	arg	`4.1.3`	indirect
npm	assertion-error	`2.0.1`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`5.0.5`	indirect
npm	chai	`6.2.2`	indirect
npm	convert-source-map	`2.0.0`	indirect
npm	create-require	`1.1.1`	indirect
npm	detect-libc	`2.1.2`	indirect
npm	diff	`4.0.4`	indirect
npm	es-module-lexer	`2.0.0`	indirect
npm	estree-walker	`3.0.3`	indirect
npm	expect-type	`1.3.0`	indirect
npm	fdir	`6.5.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	glob	`13.0.6`	indirect
npm	lightningcss	`1.32.0`	indirect
npm	lightningcss-android-arm64	`1.32.0`	indirect
npm	lightningcss-darwin-arm64	`1.32.0`	indirect
npm	lightningcss-darwin-x64	`1.32.0`	indirect
npm	lightningcss-freebsd-x64	`1.32.0`	indirect
npm	lightningcss-linux-arm-gnueabihf	`1.32.0`	indirect
npm	lightningcss-linux-arm64-gnu	`1.32.0`	indirect
npm	lightningcss-linux-arm64-musl	`1.32.0`	indirect
npm	lightningcss-linux-x64-gnu	`1.32.0`	indirect
npm	lightningcss-linux-x64-musl	`1.32.0`	indirect
npm	lightningcss-win32-arm64-msvc	`1.32.0`	indirect
npm	lightningcss-win32-x64-msvc	`1.32.0`	indirect
npm	lru-cache	`11.2.7`	indirect
npm	magic-string	`0.30.21`	indirect
npm	make-error	`1.3.6`	indirect
npm	minimatch	`10.2.4`	indirect
npm	minipass	`7.1.3`	indirect
npm	nanoid	`3.3.11`	indirect
npm	obug	`2.1.1`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-scurry	`2.0.2`	indirect
npm	pathe	`2.0.3`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.4`	indirect
npm	postcss	`8.5.8`	indirect
npm	rimraf	`6.1.3`	indirect
npm	rolldown	`1.0.0-rc.12`	indirect
npm	siginfo	`2.0.0`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	stackback	`0.0.2`	indirect
npm	std-env	`4.0.0`	indirect
npm	tinybench	`2.9.0`	indirect
npm	tinyexec	`1.0.4`	indirect
npm	tinyglobby	`0.2.15`	indirect
npm	tinyrainbow	`3.1.0`	indirect
npm	ts-node	`10.9.2`	indirect
npm	tslib	`2.8.1`	indirect
npm	typescript	`5.9.3`	indirect
npm	undici-types	`6.21.0`	indirect
npm	v8-compile-cache-lib	`3.0.1`	indirect
npm	vite	`8.0.3`	indirect
npm	vitest	`4.1.2`	indirect
npm	why-is-node-running	`2.3.0`	indirect
npm	yn	`3.1.1`	indirect

Dependency advisories 4

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

Package	Version	Relation	Severity	Advisories	Fixed in
brace-expansion	`5.0.5`	indirect	high	4	`5.0.9`
nanoid	`3.3.11`	indirect	high	2	`5.1.16`
postcss	`8.5.8`	indirect	high	4	`8.5.23`
vite	`8.0.3`	indirect	high	5	`8.0.16`

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