Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 10:51 UTC

surveyjs / survey-pdf

Supplementary component to the SurveyJS Form Library to download surveys as PDF files and generate editable PDF forms.

TypeScriptCustom license★ 89 stars⑂ 40 forkssince Apr 2019View on GitHub ↗

surveyjs/survey-pdf holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (100/100) and lowest on Security (56/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

SurveyJSOrganization
480 followers63 public repossince Jan 2017

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

Package ecosystems

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 2 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume132 commits in the last year
10/10OpenSSF Scorecard: Maintained22 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year132
human_commit_share
days_since_last_push2
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~3.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv2.5.34
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases3.9
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?

68Good · 17% of overall
How it's scored
31.5/60Stars89 stars
13.3/25Forks40 forks
3.3/15Watchers5 watchers
Inputs used
forks40
stars89
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
67.5/80Monthly downloads115,692 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessurvey-pdf
dependents
ecosystemsnpm
total_downloads
monthly_downloads115,692
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?

81Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.5/22.5Commit distributiontop contributor authored 35% of commits
13.5/13.5Contributor breadth18 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled18
top_contributor_share0.354
How it's scored
38.5/42Issue resolution92% of issues closed
28.5/30PR acceptance189/199 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/22 approved changesets -- score normalized to 0
Inputs used
merged_prs189
open_issues26
closed_issues286
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.917
closed_unmerged_prs10
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
19.3/25Owner reach480 followers of surveyjs
25/25Track record63 public repos, account ~9 yr old
Inputs used
followers480
owner_typeOrganization
is_verified
owner_loginsurveyjs
public_repos63
account_age_days3,466
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 2 days ago
20/20Version history481 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessurvey-pdf
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://surveyjs.io/pdf-generator/examples/survey-pdf-export/
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicssurveyjs, survey, pdf, pdf-generation, survey-pdf, print-survey, export-survey, pdf-generator
has_wikiyes
homepagehttps://surveyjs.io/pdf-generator/examples/survey-pdf-export/
docs_sitehttps://surveyjs.io/pdf-generator/examples/survey-pdf-export/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/22 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained22 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

74Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes6,129
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
53.8/55Manageable file sizes3/136 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes1,879,763
source_files_sampled136
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
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

89GitHub stars
18contributors
132commits, last 12 months
2days since last push
100releases
2bus factor
26open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-07-17 10:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/22 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained22 commit(s) and 22 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@types/node-fetch^2.6.13package.json
npmimage-size^2.0.2package.json
npmjspdf^4.0.0package.json
npmnode-fetch^2package.json
npmnode-interval-tree^1.3.3package.json
npmsurvey-corelatestpackage.json
All dependencies 33

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

RegistryPackageVersionRelation
npm@types/node-fetch^2.6.13direct
npmimage-size^2.0.2direct
npmjspdf^4.0.0direct
npmnode-fetch^2direct
npmnode-interval-tree^1.3.3direct
npmsurvey-corelatestdirect
npm@rollup/plugin-commonjs^28.0.2indirect
npm@rollup/plugin-node-resolve^16.0.0indirect
npm@rollup/plugin-replace^6.0.2indirect
npm@rollup/plugin-terser^0.4.4indirect
npm@rollup/plugin-typescript^12.1.2indirect
npm@stylistic/eslint-plugin^3.1.0indirect
npm@types/lodash4.14.121indirect
npm@typescript-eslint/eslint-plugin^5.41.0indirect
npm@typescript-eslint/parser^5.41.0indirect
npm@vitest/coverage-v8^4.1.5indirect
npmconcurrently^5.2.0indirect
npmdotenv4.0.0indirect
npmeslint^8indirect
npmeslint-plugin-unused-imports^2indirect
npmgenerate-json-webpack-plugin0.2.1indirect
npmhttp-server^14.1.1indirect
npmhusky^2.7.0indirect
npmjsdom^29.1.1indirect
npmrimraf2.5.4indirect
npmrollup^4.34.8indirect
npmrollup-plugin-esbuild^6.2.1indirect
npmrollup-plugin-license^3.6.0indirect
npmstandard-version^9.5.0indirect
npmts-loader^9.5.2indirect
npmtslib^2.8.1indirect
npmtypescript^5.7.0indirect
npmvitest^4.1.5indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.