Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 16:18 UTC

expo / material-symbols

TypeScript · JavaScriptNo license detected★ 3 stars⑂ 0 forkssince Mar 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

expo/material-symbols holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (72/100) and lowest on Security (1/100). It was last updated 153 days ago. A single contributor accounts for most of its recent work.

42
overall / 100
Weak

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.

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

Ownership

ExpoOrganization · verified domain
4,887 followers474 public repossince May 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@expo/material-symbols0.1.1328,3763176 days agoandroidexpoexpo-uiiconsjetpack-composematerial-designmaterial-symbolsreact-nativevector-drawable

Metrics by category

Vitality

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

54Moderate · 21% of overall

Development activity

30At Risk
How it's scored
9.9/36Push recency — last push 153 days ago
4.8/36Commit cadence — 7/52 weeks with commits
12.4/18Commit volume — 23 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year23
human_commit_share0.957
days_since_last_push153
active_weeks_last_year7

Release discipline

90Excellent
How it's scored
27/27Ships releases — 2 releases published
27/36Release recency — latest release 176 days ago
27/27Release cadence — a release every ~34 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv0.1.1
releases_from_tagsno
days_since_latest_release176
mean_days_between_releases34

Community & Adoption

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

34At Risk · 17% of overall

Popularity & adoption

5Critical
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars3
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

92Excellent
How it's scored
73.6/80Monthly downloads — 328,376 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@expo/material-symbols
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads328,376
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?

72Good · 23% of overall

Maintainer resilience (bus factor)

23At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.2/22.5Commit distribution — top contributor authored 59% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.591

Issue & PR responsiveness

87Excellent
How it's scored
0/42Issue resolution — no issues or no data
26.2/30PR acceptance — 14/16 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs14
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

100Exceptional
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 4,887 followers of expo
25/25Track record — 474 public repos, account ~11 yr old
Inputs used
followers4,887
owner_typeOrganization
is_verifiedyes
owner_loginexpo
public_repos474
account_age_days4,174

Package maintenance

92Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 176 days ago
12/20Version history — 3 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@expo/material-symbols
ecosystemsnpm
any_deprecatedno
min_days_since_publish176

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall

Engineering practices

60Moderate
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
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

30At Risk
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

1Critical · 16% of overall

Security posture

1Critical
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsexample/package.json, package.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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.

60Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 19 of 22 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.864
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

46Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — example/tsconfig.json, packages/expo-material-symbols/tsconfig.json
0/10Reproducible environment
8.7/10Demonstrated agent practice — 1 of the last 23 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsexample/tsconfig.json, packages/expo-material-symbols/tsconfig.json
agent_commit_share0.043
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/11 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes7,158
source_files_sampled11
oversized_source_files0

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

3GitHub stars
2contributors
23commits, last 12 months
153days since last push
2releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/expo/material-symbols: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-10-22T16:18:27Z. Please include `B39C:36C6E8:8DC865B:CDCB3DF:6ADA3751` when reporting this issue.); skipping Scorecard checks

More detail

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

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with expo/material-symbols. Read them side by side →

97expo/expoAn open-source framework for making universal native apps with React. Expo runs on Android, iOS, and the web.Exceptional96getsentry/sentry-react-nativeOfficial Sentry SDK for React NativeExceptional96expo/eas-cliFastest way to build, submit, and update iOS and Android appsExceptional93quasarframework/quasarQuasar Framework - Build high-performance VueJS user interfaces in record timeExceptional93rnmapbox/mapsA Mapbox react native module for creating custom mapsExceptional93callstack/react-native-builder-bobSimple set of CLIs to scaffold and build React Native libraries for different targetsExceptional

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.