Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 17:55 UTC

mvanede / webpack-version-file-plugin

A plugin that can be used with Webpack to generate a version file

JavaScriptMIT★ 17 stars⑂ 14 forkssince Nov 2015View on GitHub ↗

mvanede/webpack-version-file-plugin holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Security (58/100) and lowest on AI Readiness (36/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Mirko van EdePersonal account
1 follower2 public repossince May 2015

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
npmwebpack-version-file-plugin0.6.060,7481232 days agoversionfilebuilddate

Metrics by category

Vitality

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

54Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
2.1/36Commit cadence — 3/52 weeks with commits
9/18Commit volume — 9 commits in the last year
7/10OpenSSF Scorecard: Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year9
human_commit_share0.974
days_since_last_push12
active_weeks_last_year3
How it's scored
16.2/27Ships releases — 5 version tags (no GitHub releases)
36/36Release recency — latest release 32 days ago
5.4/27Release cadence — a release every ~977.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count5
latest_release_tagv0.6.0
releases_from_tagsyes
days_since_latest_release32
mean_days_between_releases977.9
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?

50Moderate · 17% of overall
How it's scored
19.5/60Stars — 17 stars
9.3/25Forks — 14 forks
1.7/15Watchers — 3 watchers
Inputs used
forks14
stars17
watchers3
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
0/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_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
63.8/80Monthly downloads — 60,748 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswebpack-version-file-plugin
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads60,748
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.5/22.5Commit distribution — top contributor authored 67% of commits
9.5/13.5Contributor breadth — 7 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.667
How it's scored
24/42Issue resolution — 57% of issues closed
24/30PR acceptance — 8/10 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 5/20 approved changesets -- score normalized to 2
Inputs used
merged_prs8
open_issues3
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.571
closed_unmerged_prs2
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
2.2/25Owner reach — 1 followers of mvanede
15.5/25Track record — 2 public repos, account ~11 yr old
Inputs used
followers1
owner_typeUser
is_verified—
owner_loginmvanede
public_repos2
account_age_days4,144
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 32 days ago
20/20Version history — 12 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswebpack-version-file-plugin
ecosystemsnpm
any_deprecatedno
min_days_since_publish32

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 1 out of 8 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/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_diryes
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.2/2.5CI-Tests — 1 out of 8 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 5/20 approved changesets -- score normalized to 2
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
5.2/7.5Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0.5/5SAST — SAST tool is not run on all commits -- score normalized to 1
1.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.9
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_packages1
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:webpack-version-file-plugin@0.6.0 runtime dependency closure — what installing the published package pulls in — 1 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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
17.3/40Legible commit history — 12 of 37 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.324
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 38
8/8Automated maintenance — 1 of the last 38 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.026
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes8,543
source_files_sampled2
oversized_source_files0

Key facts

17GitHub stars
7contributors
9commits, last 12 months
12days since last push
5releases
1bus factor
3open 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 ★ / 14 ⇿
0Stars
14Forks
3Releases

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.

03581013151412016-112020-122024-12
Major 0Minor 3Patch 0

Each point covers 8 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-26 17:54 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
1CI-Tests1 out of 8 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/20 approved changesets -- score normalized to 2
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
1SASTSAST tool is not run on all commits -- score normalized to 1
3Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmejs^6.0.1package.json
All dependencies 136

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

RegistryPackageVersionRelation
npmejs6.0.1direct
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/source-map0.3.11indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@types/estree1.0.9indirect
npm@types/json-schema7.0.15indirect
npm@types/node26.3.0indirect
npm@webassemblyjs/ast1.14.1indirect
npm@webassemblyjs/floating-point-hex-parser1.13.2indirect
npm@webassemblyjs/helper-api-error1.13.2indirect
npm@webassemblyjs/helper-buffer1.14.1indirect
npm@webassemblyjs/helper-numbers1.13.2indirect
npm@webassemblyjs/helper-wasm-bytecode1.13.2indirect
npm@webassemblyjs/helper-wasm-section1.14.1indirect
npm@webassemblyjs/ieee7541.13.2indirect
npm@webassemblyjs/leb1281.13.2indirect
npm@webassemblyjs/utf81.13.2indirect
npm@webassemblyjs/wasm-edit1.14.1indirect
npm@webassemblyjs/wasm-gen1.14.1indirect
npm@webassemblyjs/wasm-opt1.14.1indirect
npm@webassemblyjs/wasm-parser1.14.1indirect
npm@webassemblyjs/wast-printer1.14.1indirect
npm@xtuc/ieee7541.2.0indirect
npm@xtuc/long4.2.2indirect
npmacorn8.18.0indirect
npmajv8.20.0indirect
npmajv-formats2.1.1indirect
npmajv-keywords5.1.0indirect
npmansi-colors4.1.3indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbaseline-browser-mapping2.11.19indirect
npmbinary-extensions2.2.0indirect
npmbrace-expansion2.1.4indirect
npmbraces3.0.3indirect
npmbrowser-stdout1.3.1indirect
npmbrowserslist4.28.8indirect
npmbuffer-from1.1.2indirect
npmcamelcase6.3.0indirect
npmcaniuse-lite1.0.30001810indirect
npmchalk4.1.2indirect
npmchokidar3.5.3indirect
npmchrome-trace-event1.0.3indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommander2.20.3indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdiff5.2.2indirect
npmelectron-to-chromium1.5.414indirect
npmemoji-regex8.0.0indirect
npmenhanced-resolve5.24.5indirect
npmes-module-lexer2.3.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmeslint-scope5.1.1indirect
npmesrecurse4.3.0indirect
npmestraverse4.3.0indirect
npmestraverse5.3.0indirect
npmevents3.3.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.6indirect
npmfill-range7.1.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.2indirect
npmget-caller-file2.0.5indirect
npmglob8.1.0indirect
npmglob-parent5.1.2indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmjest-worker27.5.1indirect
npmjs-yaml4.3.2indirect
npmjson-schema-traverse1.0.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmmerge-stream2.0.0indirect
npmmime-db1.54.0indirect
npmminimatch5.1.9indirect
npmminimizer-webpack-plugin5.6.1indirect
npmmocha10.8.2indirect
npmms2.1.3indirect
npmneo-async2.6.2indirect
npmnode-releases2.0.53indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmschema-utils4.3.3indirect
npmserialize-javascript7.0.5indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.21indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtapable2.3.3indirect
npmterser5.50.0indirect
npmto-regex-range5.0.1indirect
npmundici-types8.3.0indirect
npmupdate-browserslist-db1.3.1indirect
npmwatchpack2.5.2indirect
npmwebpack5.109.2indirect
npmwebpack-sources3.5.1indirect
npmworkerpool6.5.1indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.9indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:webpack-version-file-plugin@0.6.0 pulls in 1 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.