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

brillout / vite-plugin-server-entry

Handles the server production entry.

TypeScriptNo license detected★ 10 stars⑂ 4 forkssince Aug 2022View on GitHub ↗
KindLibraryhow this is determined

brillout/vite-plugin-server-entry holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Vitality (67/100) and lowest on Engineering Quality (30/100). It was last updated 30 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

RomPersonal account
1,405 followers403 public repossince Aug 2011

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 publish
npm@brillout/vite-plugin-server-entry0.7.21303,03712230 days ago

Metrics by category

Vitality

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

67Good · 21% of overall

Development activity

53Moderate
How it's scored
28.8/36Push recency — last push 30 days ago
4.8/36Commit cadence — 7/52 weeks with commits
14.8/18Commit volume — 43 commits in the last year
5/10OpenSSF Scorecard: Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year43
human_commit_share1
days_since_last_push30
active_weeks_last_year7

Release discipline

88Excellent
How it's scored
16.2/27Ships releases — 91 version tags (no GitHub releases)
36/36Release recency — latest release 30 days ago
27/27Release cadence — a release every ~43 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count91
latest_release_tagv0.7.21
releases_from_tagsyes
days_since_latest_release30
mean_days_between_releases43
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?

40Weak · 17% of overall

Popularity & adoption

20At Risk
How it's scored
15.5/60Stars — 10 stars
4/25Forks — 4 forks
0/15Watchers — 1 watchers
Inputs used
forks4
stars10
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

91Excellent
How it's scored
73.1/80Monthly downloads — 303,037 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@brillout/vite-plugin-server-entry
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads303,037
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?

64Moderate · 23% of overall

Maintainer resilience (bus factor)

23At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.1/22.5Commit distribution — top contributor authored 100% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.996

Issue & PR responsiveness

75Good
How it's scored
42/42Issue resolution — 100% of issues closed
22.9/30PR acceptance — 13/17 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs13
open_issues0
closed_issues20
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs4
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.

Ownership & stewardship

72Good
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
22.6/25Owner reach — 1,405 followers of brillout
25/25Track record — 403 public repos, account ~15 yr old
Inputs used
followers1,405
owner_typeUser
is_verified—
owner_loginbrillout
public_repos403
account_age_days5,505
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 30 days ago
20/20Version history — 122 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@brillout/vite-plugin-server-entry
ecosystemsnpm
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall

Engineering practices

16Critical
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
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?

36Weak · 16% of overall

Security posture

20At Risk
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 4 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
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 7 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
3.8/7.5Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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 — 27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
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:@brillout/vite-plugin-server-entry@0.7.21 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.

48Weak · 4% of overall

Agent context & guidance

34At Risk
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
33.6/40Legible commit history — 63 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.63
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

38Weak
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/35 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes20,989
source_files_sampled35
oversized_source_files0

Key facts

10GitHub stars
3contributors
43commits, last 12 months
30days since last push
91releases
1bus factor
0open 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 ★ / 4 ⇿
0Stars
4Forks
85Releases

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.

1223344412022-122024-072026-02
Major 0Minor 6Patch 79

Each point covers 3 days.

OpenSSF Scorecard 2.0 / 10
2.0aggregate

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-21 21:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 7 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@brillout/import^0.2.6package.json
npm@brillout/picocolors^1.0.26package.json
All dependencies 125

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

RegistryPackageVersionRelation
npm@brillout/import0.2.6direct
npm@brillout/picocolors1.0.26direct
npm@brillout/picocolors1.0.30direct
npm@biomejs/biome1.8.3indirect
npm@biomejs/cli-darwin-arm641.8.3indirect
npm@biomejs/cli-darwin-x641.8.3indirect
npm@biomejs/cli-linux-arm641.8.3indirect
npm@biomejs/cli-linux-arm64-musl1.8.3indirect
npm@biomejs/cli-linux-x641.8.3indirect
npm@biomejs/cli-linux-x64-musl1.8.3indirect
npm@biomejs/cli-win32-arm641.8.3indirect
npm@biomejs/cli-win32-x641.8.3indirect
npm@brillout/release-me0.4.15indirect
npm@conventional-changelog/git-client2.7.0indirect
npm@esbuild/aix-ppc640.25.9indirect
npm@esbuild/android-arm0.25.9indirect
npm@esbuild/android-arm640.25.9indirect
npm@esbuild/android-x640.25.9indirect
npm@esbuild/darwin-arm640.25.9indirect
npm@esbuild/darwin-x640.25.9indirect
npm@esbuild/freebsd-arm640.25.9indirect
npm@esbuild/freebsd-x640.25.9indirect
npm@esbuild/linux-arm0.25.9indirect
npm@esbuild/linux-arm640.25.9indirect
npm@esbuild/linux-ia320.25.9indirect
npm@esbuild/linux-loong640.25.9indirect
npm@esbuild/linux-mips64el0.25.9indirect
npm@esbuild/linux-ppc640.25.9indirect
npm@esbuild/linux-riscv640.25.9indirect
npm@esbuild/linux-s390x0.25.9indirect
npm@esbuild/linux-x640.25.9indirect
npm@esbuild/netbsd-arm640.25.9indirect
npm@esbuild/netbsd-x640.25.9indirect
npm@esbuild/openbsd-arm640.25.9indirect
npm@esbuild/openbsd-x640.25.9indirect
npm@esbuild/openharmony-arm640.25.9indirect
npm@esbuild/sunos-x640.25.9indirect
npm@esbuild/win32-arm640.25.9indirect
npm@esbuild/win32-ia320.25.9indirect
npm@esbuild/win32-x640.25.9indirect
npm@rollup/rollup-android-arm-eabi4.48.1indirect
npm@rollup/rollup-android-arm644.48.1indirect
npm@rollup/rollup-darwin-arm644.48.1indirect
npm@rollup/rollup-darwin-x644.48.1indirect
npm@rollup/rollup-freebsd-arm644.48.1indirect
npm@rollup/rollup-freebsd-x644.48.1indirect
npm@rollup/rollup-linux-arm-gnueabihf4.48.1indirect
npm@rollup/rollup-linux-arm-musleabihf4.48.1indirect
npm@rollup/rollup-linux-arm64-gnu4.48.1indirect
npm@rollup/rollup-linux-arm64-musl4.48.1indirect
npm@rollup/rollup-linux-loongarch64-gnu4.48.1indirect
npm@rollup/rollup-linux-ppc64-gnu4.48.1indirect
npm@rollup/rollup-linux-riscv64-gnu4.48.1indirect
npm@rollup/rollup-linux-riscv64-musl4.48.1indirect
npm@rollup/rollup-linux-s390x-gnu4.48.1indirect
npm@rollup/rollup-linux-x64-gnu4.48.1indirect
npm@rollup/rollup-linux-x64-musl4.48.1indirect
npm@rollup/rollup-win32-arm64-msvc4.48.1indirect
npm@rollup/rollup-win32-ia32-msvc4.48.1indirect
npm@rollup/rollup-win32-x64-msvc4.48.1indirect
npm@simple-libs/child-process-utils1.0.2indirect
npm@simple-libs/stream-utils1.2.0indirect
npm@types/estree1.0.8indirect
npm@types/node15.14.9indirect
npm@types/normalize-package-data2.4.4indirect
npmarray-ify1.0.0indirect
npmcommander11.1.0indirect
npmcompare-func2.0.0indirect
npmconventional-changelog7.0.2indirect
npmconventional-changelog-angular8.0.0indirect
npmconventional-changelog-preset-loader5.0.0indirect
npmconventional-changelog-writer8.4.0indirect
npmconventional-commits-filter5.0.0indirect
npmconventional-commits-parser6.4.0indirect
npmcross-spawn7.0.3indirect
npmdot-prop5.3.0indirect
npmesbuild0.25.9indirect
npmexeca5.1.1indirect
npmfd-package-json1.2.0indirect
npmfdir6.5.0indirect
npmfsevents2.3.3indirect
npmget-stream6.0.1indirect
npmhandlebars4.7.7indirect
npmhosted-git-info8.1.0indirect
npmhuman-signals2.1.0indirect
npmis-obj2.0.0indirect
npmis-stream2.0.1indirect
npmisexe2.0.0indirect
npmlru-cache10.1.0indirect
npmlru-cache6.0.0indirect
npmmeow13.2.0indirect
npmmerge-stream2.0.0indirect
npmmimic-fn2.1.0indirect
npmminimist1.2.8indirect
npmnanoid3.3.11indirect
npmneo-async2.6.2indirect
npmnormalize-package-data7.0.1indirect
npmnpm-run-path4.0.1indirect
npmonetime5.1.2indirect
npmpath-key3.1.1indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.3indirect
npmpostcss8.5.6indirect
npmprettier3.3.3indirect
npmrollup4.48.1indirect
npmsemver7.5.4indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit3.0.7indirect
npmsource-map0.6.1indirect
npmsource-map-js1.2.1indirect
npmspdx-correct3.1.1indirect
npmspdx-exceptions2.3.0indirect
npmspdx-expression-parse3.0.1indirect
npmspdx-license-ids3.0.12indirect
npmstrip-final-newline2.0.0indirect
npmtinyglobby0.2.14indirect
npmtypescript5.7.3indirect
npmuglify-js3.17.4indirect
npmvalidate-npm-package-license3.0.4indirect
npmvite7.1.3indirect
npmwalk-up-path3.0.1indirect
npmwhich2.0.2indirect
npmwordwrap1.0.0indirect
npmyallist4.0.0indirect
Dependency advisories 0

Installing npm:@brillout/vite-plugin-server-entry@0.7.21 pulls in 2 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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with brillout/vite-plugin-server-entry. Read them side by side →

100dotnet/aspnetcoreASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.Exceptional100coder/coderSecure environments for developers and their agentsExceptional100nodejs/undiciAn HTTP/1.1 client, written from scratch for Node.jsExceptional100eslint/eslintFind and fix problems in your JavaScript code.Exceptional100microsoft/onnxruntimeONNX Runtime: cross-platform, high performance ML inferencing and training acceleratorExceptional100mlco2/codecarbonTrack emissions from Compute and recommend ways to reduce their impact on the environment.Exceptional

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.