# YanYuanFE/react-native-signature-canvas — health index 19/100 (Critical)

> Inspection of the public repository YanYuanFE/react-native-signature-canvas by inspect.software. It holds a health index of 19 out of 100, placing it in the Critical band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/YanYuanFE/react-native-signature-canvas
- Report page: https://inspect.software/software/YanYuanFE/react-native-signature-canvas
- Full JSON report: https://inspect.software/api/repositories/YanYuanFE/react-native-signature-canvas/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/y/YanYuanFE/react-native-signature-canvas.svg
- Inspected: 2026-09-15
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 72/100 | Good |
| Community & Adoption | 17% | 68/100 | Good |
| Sustainability & Governance | 23% | 54/100 | Moderate |
| Engineering Quality | 19% | 48/100 | Weak |
| Security | 16% | 30/100 | At Risk |
| AI Readiness | 4% | 67/100 | Good |

The weighted overall 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02). A dependency reported as a malicious package applies a 35% multiplier to weighted overall health and gives it a Critical ceiling of 19.

## Repository facts

| Field | Value |
|---|---|
| Description | :black_nib: React Native Signature Component based  WebView Canvas for Android && IOS && expo |
| Classification | library |
| Primary language | JavaScript |
| License | MIT |
| Stars | 506 |
| Forks | 165 |
| Created | 2018-08-13 |
| Last push | 2026-09-12 |
| Latest release | v5.1.1 |
| Commits (last year) | 20 |
| Bus factor | 1 |
| Topics | react-native, signature, expo, canvas |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | react-native-signature-canvas | 5.1.1 | 770,324 |

## Vitality — 72/100 (Good)

Is the project alive — is code being written and are releases shipping? Weight: 21% of the overall index.

### Development activity — 64/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 3 days ago |
| Commit cadence | partial | 6.2 / 36 | 9/52 weeks with commits |
| Commit volume | partial | 11.9 / 18 | 20 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 8 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 |

### Release discipline — 84/100 (Excellent)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 7 releases published |
| Release recency | met | 36 / 36 | latest release 40 days ago |
| Release cadence | partial | 12.6 / 27 | a release every ~332.5 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 40 days ago |

## Community & Adoption — 68/100 (Good)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 17% of the overall index.

### Popularity & adoption — 64/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 43.9 / 60 | 506 stars |
| Forks | partial | 18.5 / 25 | 165 forks |
| Watchers | partial | 1.7 / 15 | 3 watchers |

### Community health — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (MIT) |
| CONTRIBUTING guide | not met | 0 / 18 | — |
| Code of conduct | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

### Ecosystem adoption (downloads) — 98/100 (Exceptional)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 78.5 / 80 | 770,324 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 54/100 (Moderate)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 23% of the overall index.

### Maintainer resilience (bus factor) — 31/100 (At Risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 5.9 / 22.5 | top contributor authored 74% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 30 contributors |
| OpenSSF Scorecard: Contributors | partial | 3 / 10 | project has 1 contributing companies or organizations -- score normalized to 3 |

### Issue & PR responsiveness — 38/100 (Weak)

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 24.3 / 42 | 58% of issues closed |
| PR acceptance | partial | 5.8 / 30 | 47/242 decided PRs merged |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | partial | 3 / 15 | Found 6/23 approved changesets -- score normalized to 2 |

### Ownership & stewardship — 62/100 (Moderate)

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | partial | 10 / 30 | personal (user) account |
| Verified domain | excluded | 0 / 20 | not applicable to user accounts |
| Owner reach | partial | 15 / 25 | 122 followers of YanYuanFE |
| Track record | met | 25 / 25 | 149 public repos, account ~10 yr old |

### Package maintenance — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on npm |
| Publish recency | met | 35 / 35 | latest publish 40 days ago |
| Version history | met | 20 / 20 | 55 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 48/100 (Weak)

Are baseline engineering and documentation practices in place? Weight: 19% of the overall index.

### Engineering practices — 40/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .eslintrc.js |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | not met | 0 / 20 | 0 out of 6 merged PRs checked by a CI test -- score normalized to 0 |

### Documentation — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 4 topics |
| Wiki | met | 10 / 10 | — |

## Security — 30/100 (At Risk)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 13/100 (Critical)

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. A dependency reported as a malicious package applies a 35% multiplier to Security posture and gives it a Critical ceiling of 19.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | partial | 6.8 / 7.5 | binaries present in source code |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | not met | 0 / 2.5 | 0 out of 6 merged PRs checked by a CI test -- score normalized to 0 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | partial | 1.5 / 7.5 | Found 6/23 approved changesets -- score normalized to 2 |
| Contributors | partial | 0.8 / 2.5 | project has 1 contributing companies or organizations -- score normalized to 3 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 8 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | excluded | 0 / 5 | no dependencies found |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | not met | 0 / 7.5 | 165 existing vulnerabilities detected |

### Dependency advisories — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 2705 resolved dependencies against OSV; 3 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). 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.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 35/100 (Weak)

1 resolved dependency(ies) resolve to a version the registry still serves and the OpenSSF corpus reports as malicious. Direct and indirect are treated alike: an install-time payload runs at any depth in the graph. A report here concerns the package as published, not the maintainers of this repository, which may have resolved it unknowingly.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | partial | 35 / 100 | 1 reported as malicious: fsevents 1.2.9 |

### High-Risk Jurisdiction Exposure — 100/100 (Exceptional)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 67/100 (Good)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 35/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | partial | 34.7 / 40 | 65 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 74/100 (Good)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | example/signapp/android/app/build.gradle, example/signapp/android/build.gradle (toolchain convention, no task runner) |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc.js |
| Static type checking | met | 11 / 11 | example/signapp/tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

### Code legibility for models — 82/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | partial | 27 / 45 | JavaScript with type-check config (example/signapp/tsconfig.json) |
| Manageable file sizes | met | 55 / 55 | 0/22 source files over 60KB |

### Machine-readable interfaces — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | excluded | 0 / 40 | not applicable to this kind of software |
| MCP server | excluded | 0 / 20 | not applicable to this kind of software |
| Runnable examples | met | 40 / 40 | example |

## Collection warnings

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

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt