react-pdf-kit / react-pdf-viewer
React PDF Kit is a feature-rich React PDF Viewer component. Powered by PDF.js, it offers seamless integration with PDF documents. With customizable toolbars, search, and smooth navigation, it’s designed to deliver a professional PDF viewing experience.
react-pdf-kit/react-pdf-viewer holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on Vitality (88/100) and lowest on AI Readiness (1/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.
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.
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 42 is calibrated to 38 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 3 days ago |
| 20.1/36 | Commit cadence — 29/52 weeks with commits |
| 15.8/18 | Commit volume — 56 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — no data |
Inputs used
| commits_last_year | 56 |
| human_commit_share | — |
| days_since_last_push | 3 |
| active_weeks_last_year | 29 |
Release discipline
How it's scored
| 27/27 | Ships releases — 27 releases published |
| 36/36 | Release recency — latest release 3 days ago |
| 27/27 | Release cadence — a release every ~12.2 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 27 |
| latest_release_tag | v2.7.3 |
| releases_from_tags | no |
| days_since_latest_release | 3 |
| mean_days_between_releases | 12.2 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 24.2/60 | Stars — 32 stars |
| 4/25 | Forks — 4 forks |
| 0/15 | Watchers — 1 watchers |
Inputs used
| forks | 4 |
| stars | 32 |
| watchers | 1 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 0/22.5 | License — no license file detected |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | no |
| readme_badges | — |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 4.7/22.5 | Commit distribution — top contributor authored 79% of commits |
| 8.1/13.5 | Contributor breadth — 6 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — no data |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 6 |
| top_contributor_share | 0.792 |
Issue & PR responsiveness
How it's scored
| 36.5/42 | Issue resolution — 87% of issues closed |
| 30/30 | PR acceptance — 9/9 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — no data |
Inputs used
| merged_prs | 9 |
| open_issues | 7 |
| closed_issues | 47 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.87 |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 5/25 | Owner reach — 4 followers of react-pdf-kit |
| 13.6/25 | Track record — 25 public repos, account ~1 yr old |
Inputs used
| followers | 4 |
| owner_type | Organization |
| is_verified | — |
| owner_login | react-pdf-kit |
| public_repos | 25 |
| account_age_days | 603 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 0/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | no |
| has_tests | no |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://www.react-pdf-kit.dev |
| 10/10 | Repository description |
| 10/10 | Topics — 12 topics |
| 0/10 | Wiki |
Inputs used
| topics | javascript, nextjs, pdf-viewer-react, react, react-pdf, react-pdf-viewer, reactjs, typescript, pdf-viewer, pdfjs, pdfjs-dist, react-pdf-kit |
| has_wiki | no |
| homepage | https://www.react-pdf-kit.dev |
| docs_site | https://www.react-pdf-kit.dev |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 0/30 | Security policy (SECURITY.md) |
| 0/25 | Dependabot config |
| 0/25 | Dependency lockfiles — no dependency manifests — not applicable |
| 0/20 | CodeQL workflow |
Inputs used
| source | file_signals |
| lockfiles | — |
| manifests | — |
| has_codeql_workflow | no |
| has_security_policy | no |
| has_dependabot_config | no |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 0/18 | One-command bootstrap |
| 0/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | no |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | — |
Code legibility for models
How it's scored
| 0/45 | Type-checkable code — CSS without a type-check config |
| 0/55 | Manageable file sizes — no source files detected |
Inputs used
| primary_language | CSS |
| largest_source_bytes | — |
| source_files_sampled | 0 |
| oversized_source_files | 0 |
Key facts
Data collection warnings
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
- OpenSSF Scorecard timed out after 240s; 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.
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.11.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics.