Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 05:10 UTC

empjs / emp

EMP Micro FE Base on Rspack & module federation

TypeScript · JavaScriptNo license detected★ 2,398 stars⑂ 230 forkssince Oct 2020View on GitHub ↗
KindWeb interfaceLibraryhow this is determined

empjs/emp holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (88/100) and lowest on Security (44/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

empjsOrganization
12 followers8 public repossince Oct 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmmf-app0.0.0611490 days ago
npmtailwind-demo00
npmvue-3-base-0

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
22.2/36Commit cadence32/52 weeks with commits
18/18Commit volume499 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year499
human_commit_share1
days_since_last_push0
active_weeks_last_year32
How it's scored
27/27Ships releases41 releases published
36/36Release recencylatest release 5 days ago
27/27Release cadencea release every ~42.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count41
latest_release_tagv4.0.0
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases42.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

59Moderate · 17% of overall
How it's scored
54.8/60Stars2,398 stars
19.7/25Forks230 forks
8/15Watchers28 watchers
Inputs used
forks230
stars2,398
watchers28
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11.1/22.5Commit distributiontop contributor authored 51% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.506
How it's scored
42/42Issue resolution100% of issues closed
24.4/30PR acceptance92/113 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs92
open_issues0
closed_issues227
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs21
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
8/25Owner reach12 followers of empjs
12.5/25Track record8 public repos, account ~2 yr old
Inputs used
followers12
owner_typeOrganization
is_verified
owner_loginempjs
public_repos8
account_age_days1,005
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable3 package(s) on npm
4/35Publish recencylatest publish 1,490 days ago
4/20Version history1 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmf-app, tailwind-demo, vue-3-base
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,490

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://v4.empjs.dev
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsemp, federation, module-federation
has_wikiyes
homepagehttps://v4.empjs.dev
docs_sitehttps://v4.empjs.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/28 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4
How it's scored
9.2/35Direct dependencies free of known advisories3 affected: @angular/common 14.0.7 (high 8.2), @angular/compiler 14.0.7 (moderate 6.1), @angular/core 14.0.7 (moderate 6.1)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
26.5/40No advisories left outstanding3 advisory-carrying package(s) unaddressed past 90 days; oldest published 237 days ago
Inputs used
sourceosv
advisories14
affected_packages3
assessed_packages12
unassessed_packages0
affected_by_severityhigh 1, moderate 2
direct_affected_packages3
Matched the npm:mf-app@0.0.0 runtime dependency closure — what installing the published package pulls in — 12 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.

68Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,601
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingapps/adapter-app/tsconfig.json, apps/adapter-host/tsconfig.json, apps/demo/tsconfig.json, apps/dual-role/tsconfig.json, apps/mf-app/tsconfig.json, apps/mf-host/tsconfig.json, apps/react-19-tanstack/tsconfig.json, apps/tailwind-4/tsconfig.json, apps/vue-2-base/tsconfig.json, apps/vue-2-project/tsconfig.json, apps/vue-3-base/tsconfig.json, apps/vue-3-project/tsconfig.json, packages/adapter-react/tsconfig.json, packages/bridge-react/tsconfig.json, packages/bridge-vue2/tsconfig.json, packages/bridge-vue3/tsconfig.json, packages/cdn-react-17/tsconfig.json, packages/cdn-react-18/tsconfig.json, packages/cdn-react-19-tanstack-router/tsconfig.json, packages/cdn-react-19/tsconfig.json, packages/cdn-react-wouter/tsconfig.json, packages/cdn-vue-2/tsconfig.json, packages/cdn-vue-3/tsconfig.json, packages/cdn-vue-router-pinia/tsconfig.json, packages/cli/tsconfig.json, packages/emp-chain/tsconfig.json, packages/emp-polyfill/tsconfig.json, packages/emp-share/tsconfig.json, packages/lib-react-17/tsconfig.json, packages/lib-vue-2/tsconfig.json, packages/plugin-lightningcss/tsconfig.json, packages/plugin-postcss/tsconfig.json, packages/plugin-react/tsconfig.json, packages/plugin-stylus/tsconfig.json, packages/plugin-tailwindcss/tsconfig.json, packages/plugin-vue2/tsconfig.json, packages/plugin-vue3/tsconfig.json, website/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsapps/adapter-app/tsconfig.json, apps/adapter-host/tsconfig.json, apps/demo/tsconfig.json, apps/dual-role/tsconfig.json, apps/mf-app/tsconfig.json, apps/mf-host/tsconfig.json, apps/react-19-tanstack/tsconfig.json, apps/tailwind-4/tsconfig.json, apps/vue-2-base/tsconfig.json, apps/vue-2-project/tsconfig.json, apps/vue-3-base/tsconfig.json, apps/vue-3-project/tsconfig.json, packages/adapter-react/tsconfig.json, packages/bridge-react/tsconfig.json, packages/bridge-vue2/tsconfig.json, packages/bridge-vue3/tsconfig.json, packages/cdn-react-17/tsconfig.json, packages/cdn-react-18/tsconfig.json, packages/cdn-react-19-tanstack-router/tsconfig.json, packages/cdn-react-19/tsconfig.json, packages/cdn-react-wouter/tsconfig.json, packages/cdn-vue-2/tsconfig.json, packages/cdn-vue-3/tsconfig.json, packages/cdn-vue-router-pinia/tsconfig.json, packages/cli/tsconfig.json, packages/emp-chain/tsconfig.json, packages/emp-polyfill/tsconfig.json, packages/emp-share/tsconfig.json, packages/lib-react-17/tsconfig.json, packages/lib-vue-2/tsconfig.json, packages/plugin-lightningcss/tsconfig.json, packages/plugin-postcss/tsconfig.json, packages/plugin-react/tsconfig.json, packages/plugin-stylus/tsconfig.json, packages/plugin-tailwindcss/tsconfig.json, packages/plugin-vue2/tsconfig.json, packages/plugin-vue3/tsconfig.json, website/tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/415 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes42,348
source_files_sampled415
oversized_source_files0

Key facts

2,398GitHub stars
19contributors
499commits, last 12 months
0days since last push
41releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Could not fetch npm package 'mf-host' from its registry
  • Could not fetch npm package 'vue-2-base' from its registry
  • Could not fetch npm package 'adapter-app' from its registry
  • Could not fetch npm package 'adapter-host' from its registry
  • Could not fetch npm package 'vue-3-project' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 2,398 ★ / 230 ⇿
2,398Stars
230Forks
38Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

04008001,2001,6002,0002,4002,398230182020-102023-092026-07
Major 0Minor 6Patch 27

Each point covers 6 days.

OpenSSF Scorecard 4.0 / 10
4.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-07-22 05:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 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/28 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities20 existing vulnerabilities detected
Direct dependencies 40
RegistryPackageVersion constraintManifest
npmreact^19.2.3website/package.json
npmreact-dom^19.2.3website/package.json
npm@empjs/bridge-reactworkspace:^apps/adapter-app/package.json
npm@empjs/bridge-vue2workspace:^apps/adapter-app/package.json
npm@empjs/bridge-vue3workspace:^apps/adapter-app/package.json
npm@empjs/shareworkspace:^apps/adapter-app/package.json
npmreact17apps/adapter-app/package.json
npmreact-dom17apps/adapter-app/package.json
npm@empjs/shareworkspace:^apps/adapter-host/package.json
npm@empjs/shareworkspace:^apps/mf-app/package.json
npm@empjs/shareworkspace:^apps/mf-host/package.json
npmcore-js^3.36.1apps/mf-host/package.json
npmmobx^6.12.3apps/mf-host/package.json
npmmobx-react^9.1.1apps/mf-host/package.json
npm@empjs/shareworkspace:^apps/react-19-tanstack/package.json
npm@tanstack/react-router^1.131.47apps/react-19-tanstack/package.json
npmtailwindcss4.3.1apps/react-19-tanstack/package.json
npm@empjs/shareworkspace:^apps/vue-2-base/package.json
npmelement-ui^2.15.14apps/vue-2-base/package.json
npmvue^2.7.14apps/vue-2-base/package.json
npmvue-router3apps/vue-2-base/package.json
npmvuex3apps/vue-2-base/package.json
npm@empjs/shareworkspace:^apps/vue-2-project/package.json
npmvue^2.7.14apps/vue-2-project/package.json
npmvue-router3apps/vue-2-project/package.json
npmvuex3apps/vue-2-project/package.json
npm@empjs/plugin-lightningcssworkspace:^apps/vue-3-base/package.json
npm@empjs/shareworkspace:^apps/vue-3-base/package.json
npmant-design-vue^4.1.2apps/vue-3-base/package.json
npmpinia^3.0.3apps/vue-3-base/package.json
npmvue^3.5.21apps/vue-3-base/package.json
npm@empjs/shareworkspace:^apps/vue-3-project/package.json
npmant-design-vue^4.1.2apps/vue-3-project/package.json
npmpinia^3.0.3apps/vue-3-project/package.json
npmvue^3.5.13apps/vue-3-project/package.json
npmvue-router4apps/vue-3-project/package.json
npm@biomejs/biome2.3.13packages/biome-config/package.json
npmreact^17.0.0packages/cdn-react-17/package.json
npmreact-dom^17.0.0packages/cdn-react-17/package.json
npmreact-router-dom^6.25.1packages/cdn-react-17/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 3

Installing npm:mf-app@0.0.0 pulls in 12 packages, direct and transitive: 3 carry known advisories, of which 3 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@angular/common14.0.7directhigh522.0.1
@angular/compiler14.0.7directmoderate422.0.1
@angular/core14.0.7directmoderate522.0.1

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.26.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.