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

pungfen / element

Element Plus Components

Vue · TypeScriptMIT★ 1 star⑂ 0 forkssince Jan 2026View on GitHub ↗
KindLibraryWeb interfacehow this is determined

pungfen/element holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (30/100). It was last updated 16 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

pengPersonal account
3 followers14 public repossince Jan 2017

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
npm@pungfe/element0.9.36768816 days agoelementelement-plusvue

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 16 days ago
14.5/36Commit cadence — 21/52 weeks with commits
18/18Commit volume — 334 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year334
human_commit_share0.9
days_since_last_push16
active_weeks_last_year21

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 20 releases published
36/36Release recency — latest release 16 days ago
27/27Release cadence — a release every ~6.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count20
latest_release_tag@pungfe/element@0.9.2
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases6.3
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?

30At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
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
37.7/80Monthly downloads — 676 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@pungfe/element
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads676
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
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 34/34 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/6 approved changesets -- score normalized to 0
Inputs used
merged_prs34
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
4.3/25Owner reach — 3 followers of pungfen
20.6/25Track record — 14 public repos, account ~9 yr old
Inputs used
followers3
owner_typeUser
is_verified—
owner_loginpungfen
public_repos14
account_age_days3,531
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 16 days ago
20/20Version history — 88 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@pungfe/element
ecosystemsnpm
any_deprecatedno
min_days_since_publish16

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 2 out of 9 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
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?

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5CI-Tests — 2 out of 9 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/6 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
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
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_packages46
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:@pungfe/element@0.9.3 runtime dependency closure — what installing the published package pulls in — 46 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.

49Weak · 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 — 84 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.933
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 — __play__/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs__play__/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Vue with type-check config (__play__/tsconfig.json, tsconfig.json)
55/55Manageable file sizes — 0/24 source files over 60KB
Inputs used
primary_languageVue
largest_source_bytes3,376
source_files_sampled24
oversized_source_files0

Key facts

1GitHub stars
1contributors
334commits, last 12 months
16days since last push
20releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-10 13:05 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests2 out of 9 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/6 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npm@pungfe/elementworkspace:*__play__/package.json
npm@vueuse/core^14.3.0__play__/package.json
npmelement-pluscatalog:__play__/package.json
npmpinia^3.0.4__play__/package.json
npmvuecatalog:__play__/package.json
npmvue-router^5.1.0__play__/package.json
npm@element-plus/icons-vue^2.3.2package.json
npm@vueuse/core^14.4.0package.json
npm@vueuse/integrations^14.4.0package.json
npmelement-pluscatalog:package.json
npmsortablejs^1.15.7package.json
npmvuecatalog:package.json
All dependencies 40

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

RegistryPackageVersionRelation
npm@vueuse/core^14.3.0direct
npmelement-pluscatalog:direct
npmpinia^3.0.4direct
npmvuecatalog:direct
npmvue-router^5.1.0direct
npm@iconify-json/ep^1.2.4indirect
npm@pnpm/exe11.6.0indirect
npm@pnpm/linux-arm6411.6.0indirect
npm@pnpm/linux-x6411.6.0indirect
npm@pnpm/linuxstatic-arm6411.6.0indirect
npm@pnpm/linuxstatic-x6411.6.0indirect
npm@pnpm/macos-arm6411.6.0indirect
npm@pnpm/win-arm6411.6.0indirect
npm@pnpm/win-x6411.6.0indirect
npm@reflink/reflink0.1.19indirect
npm@reflink/reflink-darwin-arm640.1.19indirect
npm@reflink/reflink-darwin-x640.1.19indirect
npm@reflink/reflink-linux-arm64-gnu0.1.19indirect
npm@reflink/reflink-linux-arm64-musl0.1.19indirect
npm@reflink/reflink-linux-x64-gnu0.1.19indirect
npm@reflink/reflink-linux-x64-musl0.1.19indirect
npm@reflink/reflink-win32-arm64-msvc0.1.19indirect
npm@reflink/reflink-win32-x64-msvc0.1.19indirect
npm@tailwindcss/vitecatalog:indirect
npm@types/mockjs^1.0.10indirect
npm@vitejs/plugin-vuecatalog:indirect
npm@vitejs/plugin-vue-jsxcatalog:indirect
npm@vue/tsconfig^0.9.1indirect
npmdetect-libc2.1.2indirect
npmmockjs^1.1.0indirect
npmpnpm11.6.0indirect
npmtailwindcsscatalog:indirect
npmtypescriptcatalog:indirect
npmunplugin-auto-import^21.0.0indirect
npmunplugin-icons^23.0.1indirect
npmunplugin-vue-components^32.1.0indirect
npmvitecatalog:indirect
npmvite-plugin-vue-devtools^8.1.2indirect
npmvue-component-type-helperscatalog:indirect
npmvue-tsccatalog:indirect
Dependency advisories 0

Installing npm:@pungfe/element@0.9.3 pulls in 46 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.