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

muan / emojilib

Emoji keyword library.

JavaScriptMIT★ 1,775 stars⑂ 305 forkssince Dec 2013View on GitHub ↗

muan/emojilib holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (82/100) and lowest on AI Readiness (25/100). It was last updated 131 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Mu-An ChiouPersonal account
11,384 followers152 public repossince Oct 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 publishTags
npmemojilib4.0.331,808,98744152 days agoemojikeywordsearch

Metrics by category

Vitality

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

42Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 131 days ago
2.1/36Commit cadence — 3/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year6
human_commit_share0.95
days_since_last_push131
active_weeks_last_year3
How it's scored
27/27Ships releases — 22 releases published
27/36Release recency — latest release 152 days ago
12.6/27Release cadence — a release every ~166.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count22
latest_release_tagv4.0.3
releases_from_tagsno
days_since_latest_release152
mean_days_between_releases166.1
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?

82Excellent · 17% of overall
How it's scored
52.7/60Stars — 1,775 stars
20.7/25Forks — 305 forks
7.5/15Watchers — 23 watchers
Inputs used
forks305
stars1,775
watchers23
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 31,808,987 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesemojilib
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads31,808,987
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?

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.3/22.5Commit distribution — top contributor authored 63% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 43 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.629
How it's scored
38.8/42Issue resolution — 92% of issues closed
22.5/30PR acceptance — 143/191 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 6/13 approved changesets -- score normalized to 4
Inputs used
merged_prs143
open_issues4
closed_issues48
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.923
closed_unmerged_prs48
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
25/25Owner reach — 11,384 followers of muan
25/25Track record — 152 public repos, account ~14 yr old
Inputs used
followers11,384
owner_typeUser
is_verified—
owner_loginmuan
public_repos152
account_age_days5,440
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 152 days ago
20/20Version history — 44 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesemojilib
ecosystemsnpm
any_deprecatedno
min_days_since_publish152

Engineering Quality

Are baseline engineering and documentation practices in place?

43Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 2 out of 8 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://unpkg.com/emojilib@latest
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsemoji, emoji-searcher
has_wikino
homepagehttps://unpkg.com/emojilib@latest
docs_sitehttps://unpkg.com/emojilib@latest
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

52Moderate · 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.5/2.5CI-Tests — 2 out of 8 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
3/7.5Code-Review — Found 6/13 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 43 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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 — detected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities — 7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
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
advisories7
affected_packages3
assessed_packages85
unassessed_packages0
affected_by_severityhigh 2, moderate 1
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 85 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.

25At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
15.7/40Legible commit history — 28 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.295
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/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 100
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsno
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.05
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/6 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,649
source_files_sampled6
oversized_source_files0

Key facts

1,775GitHub stars
99contributors
6commits, last 12 months
131days since last push
22releases
1bus factor
4open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index npm:emojilib@4.0.3; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 305 ⇿
0Stars
305Forks
22Releases

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.

012525037530152015-072021-022026-09
Major 3Minor 4Patch 15

Each point covers 11 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-09-17 21:18 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 6/13 approved changesets -- score normalized to 4
10Contributorsproject has 43 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
All dependencies 85

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

RegistryPackageVersionRelation
npm@graphql-typed-document-node/core3.2.0indirect
npmarray-filter1.0.0indirect
npmavailable-typed-arrays1.0.2indirect
npmbalanced-match1.0.0indirect
npmbrace-expansion1.1.11indirect
npmcall-bind1.0.2indirect
npmchange-case5.4.4indirect
npmconcat-map0.0.1indirect
npmcross-fetch3.1.8indirect
npmdeep-equal2.0.5indirect
npmdefine-properties1.1.3indirect
npmdefined1.0.0indirect
npmdotignore0.1.2indirect
npmemoji-platform-data0.1.0indirect
npmemojipedia0.3.0indirect
npmes-abstract1.17.7indirect
npmes-abstract1.18.0-next.1indirect
npmes-get-iterator1.1.1indirect
npmes-to-primitive1.2.1indirect
npmfast-xml-builder1.1.4indirect
npmfast-xml-parser5.5.7indirect
npmfor-each0.3.3indirect
npmforeach2.0.5indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.1indirect
npmget-intrinsic1.0.2indirect
npmglob7.1.6indirect
npmgraphql16.8.2indirect
npmgraphql-request6.1.0indirect
npmhas1.0.3indirect
npmhas-symbols1.0.1indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-arguments1.1.0indirect
npmis-bigint1.0.1indirect
npmis-boolean-object1.1.0indirect
npmis-callable1.2.2indirect
npmis-core-module2.2.0indirect
npmis-date-object1.0.2indirect
npmis-map2.0.2indirect
npmis-negative-zero2.0.1indirect
npmis-number-object1.0.4indirect
npmis-regex1.1.1indirect
npmis-set2.0.2indirect
npmis-string1.0.5indirect
npmis-symbol1.0.3indirect
npmis-typed-array1.1.4indirect
npmis-weakmap2.0.1indirect
npmis-weakset2.0.1indirect
npmisarray2.0.5indirect
npmminimatch3.1.5indirect
npmminimist1.2.6indirect
npmmute-stream0.0.8indirect
npmnode-fetch2.7.0indirect
npmobject-inspect1.9.0indirect
npmobject-is1.1.4indirect
npmobject-keys1.1.1indirect
npmobject.assign4.1.2indirect
npmonce1.4.0indirect
npmp-throttle6.1.0indirect
npmpath-expression-matcher1.1.3indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.7indirect
npmprettier1.18.2indirect
npmpromptly3.2.0indirect
npmread1.0.7indirect
npmregexp.prototype.flags1.3.0indirect
npmresolve1.19.0indirect
npmresumer0.0.0indirect
npmside-channel1.0.4indirect
npmstring.prototype.trim1.2.3indirect
npmstring.prototype.trimend1.0.3indirect
npmstring.prototype.trimstart1.0.3indirect
npmstrnum2.2.1indirect
npmtape5.1.1indirect
npmthrough2.3.8indirect
npmtr460.0.3indirect
npmunicode-emoji-json0.4.0indirect
npmunicode-emoji-json0.9.0indirect
npmwebidl-conversions3.0.1indirect
npmwhatwg-url5.0.0indirect
npmwhich-boxed-primitive1.0.2indirect
npmwhich-collection1.0.1indirect
npmwhich-typed-array1.1.4indirect
npmwrappy1.0.2indirect
Dependency advisories 3

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion1.1.11indirecthigh55.0.9
fast-xml-builder1.1.4indirecthigh11.1.7
fast-xml-parser5.5.7indirectmoderate15.7.0

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.