Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-08 07:55 UTC

rstackjs / rspack-lite-tapable

Lite weight tapable for Rspack.

JavaScript · TypeScriptMIT★ 9 stars⑂ 4 forkssince Aug 2024View on GitHub ↗

rstackjs/rspack-lite-tapable holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (80/100) and lowest on Community & Adoption (50/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

RstackOrganization
179 followers115 public repossince Mar 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@rspack/lite-tapable1.1.526,014,8551938 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
15.9/36Commit cadence — 23/52 weeks with commits
15.8/18Commit volume — 56 commits in the last year
10/10OpenSSF Scorecard: Maintained — 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year56
human_commit_share0.545
days_since_last_push0
active_weeks_last_year23
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 38 days ago
12.6/27Release cadence — a release every ~120.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv1.1.5
releases_from_tagsno
days_since_latest_release38
mean_days_between_releases120.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?

50Moderate · 17% of overall
How it's scored
14.6/60Stars — 9 stars
4/25Forks — 4 forks
0/15Watchers — 2 watchers
Inputs used
forks4
stars9
watchers2
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 26,014,855 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@rspack/lite-tapable
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads26,014,855
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.1/22.5Commit distribution — top contributor authored 90% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.905
How it's scored
0/42Issue resolution — 0% of issues closed
28.9/30PR acceptance — 55/57 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/25 approved changesets -- score normalized to 0
Inputs used
merged_prs55
open_issues3
closed_issues0
prs_merged_7d3
prs_decided_7d3
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0
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
30/30Ownership backing — organization-owned
0/20Verified domain
16.2/25Owner reach — 179 followers of rstackjs
19.9/25Track record — 115 public repos, account ~3 yr old
Inputs used
followers179
owner_typeOrganization
is_verifiedno
owner_loginrstackjs
public_repos115
account_age_days1,260

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 38 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@rspack/lite-tapable
ecosystemsnpm
any_deprecatedno
min_days_since_publish38

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 25 out of 25 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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicsrspack, tapable
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?

70Good · 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
2.5/2.5CI-Tests — 25 out of 25 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/25 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 8 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 — 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages121
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 121 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
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 42 of 42 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 77
8/8Automated maintenance — 31 of the last 77 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_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.403
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes — 0/12 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes34,217
source_files_sampled12
oversized_source_files0

Key facts

9GitHub stars
4contributors
56commits, last 12 months
0days since last push
7releases
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 ★ / 4 ⇿
0Stars
4Forks
1Releases

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.

1223344412024-092025-052026-01
Major 0Minor 1Patch 0

Each point covers 2 days.

OpenSSF Scorecard 6.2 / 10
6.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-08 07:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests25 out of 25 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/25 approved changesets -- score normalized to 0
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 121

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

RegistryPackageVersionRelation
npm@ast-grep/napi0.45.1indirect
npm@ast-grep/napi-darwin-arm640.45.1indirect
npm@ast-grep/napi-darwin-x640.45.1indirect
npm@ast-grep/napi-linux-arm64-gnu0.45.1indirect
npm@ast-grep/napi-linux-arm64-musl0.45.1indirect
npm@ast-grep/napi-linux-x64-gnu0.45.1indirect
npm@ast-grep/napi-linux-x64-musl0.45.1indirect
npm@ast-grep/napi-win32-arm64-msvc0.45.1indirect
npm@ast-grep/napi-win32-ia32-msvc0.45.1indirect
npm@ast-grep/napi-win32-x64-msvc0.45.1indirect
npm@emnapi/core1.11.3indirect
npm@emnapi/runtime1.11.3indirect
npm@emnapi/wasi-threads1.2.3indirect
npm@napi-rs/wasm-runtime1.1.6indirect
npm@rsbuild/core2.2.1indirect
npm@rsbuild/core2.2.2indirect
npm@rslib/core1.0.0-rc.2indirect
npm@rslint/core0.9.0indirect
npm@rslint/native-darwin-arm640.9.0indirect
npm@rslint/native-darwin-x640.9.0indirect
npm@rslint/native-linux-arm64-gnu0.9.0indirect
npm@rslint/native-linux-arm64-musl0.9.0indirect
npm@rslint/native-linux-x64-gnu0.9.0indirect
npm@rslint/native-linux-x64-musl0.9.0indirect
npm@rslint/native-win32-arm64-msvc0.9.0indirect
npm@rslint/native-win32-x64-msvc0.9.0indirect
npm@rspack/binding2.2.1indirect
npm@rspack/binding2.2.2indirect
npm@rspack/binding-darwin-arm642.2.1indirect
npm@rspack/binding-darwin-arm642.2.2indirect
npm@rspack/binding-darwin-x642.2.1indirect
npm@rspack/binding-darwin-x642.2.2indirect
npm@rspack/binding-linux-arm64-gnu2.2.1indirect
npm@rspack/binding-linux-arm64-gnu2.2.2indirect
npm@rspack/binding-linux-arm64-musl2.2.1indirect
npm@rspack/binding-linux-arm64-musl2.2.2indirect
npm@rspack/binding-linux-ppc64-gnu2.2.1indirect
npm@rspack/binding-linux-ppc64-gnu2.2.2indirect
npm@rspack/binding-linux-riscv64-gnu2.2.1indirect
npm@rspack/binding-linux-riscv64-gnu2.2.2indirect
npm@rspack/binding-linux-riscv64-musl2.2.1indirect
npm@rspack/binding-linux-riscv64-musl2.2.2indirect
npm@rspack/binding-linux-s390x-gnu2.2.1indirect
npm@rspack/binding-linux-s390x-gnu2.2.2indirect
npm@rspack/binding-linux-x64-gnu2.2.1indirect
npm@rspack/binding-linux-x64-gnu2.2.2indirect
npm@rspack/binding-linux-x64-musl2.2.1indirect
npm@rspack/binding-linux-x64-musl2.2.2indirect
npm@rspack/binding-wasm32-wasi2.2.1indirect
npm@rspack/binding-wasm32-wasi2.2.2indirect
npm@rspack/binding-win32-arm64-msvc2.2.1indirect
npm@rspack/binding-win32-arm64-msvc2.2.2indirect
npm@rspack/binding-win32-ia32-msvc2.2.1indirect
npm@rspack/binding-win32-ia32-msvc2.2.2indirect
npm@rspack/binding-win32-x64-msvc2.2.1indirect
npm@rspack/binding-win32-x64-msvc2.2.2indirect
npm@rspack/core2.2.1indirect
npm@rspack/core2.2.2indirect
npm@rstackjs/cli-darwin-arm640.7.2indirect
npm@rstackjs/cli-darwin-x640.7.2indirect
npm@rstackjs/cli-linux-arm64-gnu0.7.2indirect
npm@rstackjs/cli-linux-arm64-musl0.7.2indirect
npm@rstackjs/cli-linux-ppc64-gnu0.7.2indirect
npm@rstackjs/cli-linux-riscv64-gnu0.7.2indirect
npm@rstackjs/cli-linux-riscv64-musl0.7.2indirect
npm@rstackjs/cli-linux-s390x-gnu0.7.2indirect
npm@rstackjs/cli-linux-x64-gnu0.7.2indirect
npm@rstackjs/cli-linux-x64-musl0.7.2indirect
npm@rstackjs/cli-win32-arm64-msvc0.7.2indirect
npm@rstackjs/cli-win32-ia32-msvc0.7.2indirect
npm@rstackjs/cli-win32-x64-msvc0.7.2indirect
npm@rstest/core0.11.11indirect
npm@swc/helpers0.5.23indirect
npm@tybys/wasm-util0.10.3indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/node24.13.3indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npm@yuku-parser/binding-android-arm640.9.3indirect
npm@yuku-parser/binding-darwin-arm640.9.3indirect
npm@yuku-parser/binding-darwin-x640.9.3indirect
npm@yuku-parser/binding-freebsd-x640.9.3indirect
npm@yuku-parser/binding-linux-arm-gnu0.9.3indirect
npm@yuku-parser/binding-linux-arm-musl0.9.3indirect
npm@yuku-parser/binding-linux-arm64-gnu0.9.3indirect
npm@yuku-parser/binding-linux-arm64-musl0.9.3indirect
npm@yuku-parser/binding-linux-x64-gnu0.9.3indirect
npm@yuku-parser/binding-linux-x64-musl0.9.3indirect
npm@yuku-parser/binding-win32-arm640.9.3indirect
npm@yuku-parser/binding-win32-x640.9.3indirect
npm@yuku-toolchain/types0.9.3indirect
npmassertion-error2.0.1indirect
npmpicomatch4.0.5indirect
npmprettier3.9.6indirect
npmrsbuild-plugin-dts1.0.0-rc.2indirect
npmrstack0.7.2indirect
npmtinypool2.1.2indirect
npmtslib2.8.1indirect
npmtypescript7.0.2indirect
npmundici-types7.18.2indirect
npmyuku-ast0.9.3indirect
npmyuku-parser0.9.3indirect
Dependency advisories 0

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

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.