Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-29 14:00 UTC

veraPDF / veraPDF-validation

Implementation of veraPDF validation model

JavaGPL-3.0★ 74 stars⑂ 26 forkssince Apr 2016View on GitHub ↗

veraPDF/veraPDF-validation holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on AI Readiness (41/100). It was last updated today. 2 contributors account for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

veraPDFOrganization
170 followers36 public repossince Nov 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenorg.verapdf:metadata-fixer1.30.2-4251 days ago
Mavenorg.verapdf:wcag-validation1.30.2-1351 days ago
Mavenorg.verapdf:validation-model1.30.2-4051 days ago
Mavenorg.verapdf:feature-reporting1.30.2-4251 days ago

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
24.2/36Commit cadence — 35/52 weeks with commits
16.8/18Commit volume — 74 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year74
human_commit_share1
days_since_last_push0
active_weeks_last_year35
How it's scored
16.2/27Ships releases — 31 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~0.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count31
latest_release_tagv1.31.117
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases0.6
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?

48Weak · 17% of overall
How it's scored
30.2/60Stars — 74 stars
11.7/25Forks — 26 forks
4.3/15Watchers — 7 watchers
Inputs used
forks26
stars74
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.5/22.5Commit distribution — top contributor authored 40% of commits
13.5/13.5Contributor breadth — 17 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled17
top_contributor_share0.4
How it's scored
0/42Issue resolution — no issues or no data
29.3/30PR acceptance — 708/725 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 12/30 approved changesets -- score normalized to 4
Inputs used
merged_prs708
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs17
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, newcomer_pr_acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.1/25Owner reach — 170 followers of veraPDF
23.4/25Track record — 36 public repos, account ~11 yr old
Inputs used
followers170
owner_typeOrganization
is_verified
owner_loginveraPDF
public_repos36
account_age_days4,264

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on maven
35/35Publish recency — latest publish 51 days ago
20/20Version history — 42 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesorg.verapdf:metadata-fixer, org.verapdf:wcag-validation, org.verapdf:validation-model, org.verapdf:feature-reporting
ecosystemsmaven
any_deprecatedno
min_days_since_publish51

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://verapdf.org
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttp://verapdf.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 12/30 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 8 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
7.5/7.5Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): branch_protection, packaging, signed_releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.4/25Indirect dependencies free of known advisories — 2 affected: com.fasterxml.jackson.core:jackson-core 2.21.1 (high 7.5), com.fasterxml.jackson.core:jackson-databind 2.21.1 (high 8.1)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories11
affected_packages2
assessed_packages15
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the maven:org.verapdf:metadata-fixer@1.30.2 runtime dependency closure — what installing the published package pulls in — 15 packages. 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.4/40Legible commit history — 12 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.12
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — feature-reporting/pom.xml, metadata-fixer/pom.xml, pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsfeature-reporting/pom.xml, metadata-fixer/pom.xml, pom.xml, validation-model/pom.xml, wcag-validation/pom.xml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/452 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes45,300
source_files_sampled452
oversized_source_files0

Key facts

74GitHub stars
17contributors
74commits, last 12 months
0days since last push
31releases
2bus factor
0open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 26 ⇿
0Stars
26Forks
18Releases

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.

0510152025302622016-062021-072026-07
Major 0Minor 0Patch 18

Each point covers 10 days.

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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-29 14:00 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 12/30 approved changesets -- score normalized to 4
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 0 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
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
Mavenorg.verapdf:parserfeature-reporting/pom.xml
Mavenorg.verapdf:corefeature-reporting/pom.xml
Mavenjavax.xml.bind:jaxb-api2.3.1feature-reporting/pom.xml
Mavencom.sun.xml.bind:jaxb-impl2.3.2feature-reporting/pom.xml
Mavencom.sun.xml.bind:jaxb-core2.3.0.1feature-reporting/pom.xml
Mavenorg.verapdf:parsermetadata-fixer/pom.xml
Mavenorg.verapdf:verapdf-xmp-coremetadata-fixer/pom.xml
Mavenorg.verapdf:coremetadata-fixer/pom.xml
Mavenorg.verapdf:parser${verapdf.parser.version}pom.xml
Mavenorg.verapdf:pdf-model${verapdf.pdfmodel.version}pom.xml
Mavenorg.verapdf:core${verapdf.library.version}pom.xml
Mavenorg.verapdf:verapdf-xmp-core${verapdf.library.version}pom.xml
Mavenorg.verapdf:parservalidation-model/pom.xml
Mavenorg.verapdf:pdf-modelvalidation-model/pom.xml
Mavenorg.verapdf:corevalidation-model/pom.xml
Mavenorg.verapdf:feature-reporting${project.version}validation-model/pom.xml
Mavenorg.verapdf:wcag-validation${project.version}validation-model/pom.xml
Mavenorg.verapdf:metadata-fixer${project.version}validation-model/pom.xml
Mavenorg.verapdf:parserwcag-validation/pom.xml
Mavenorg.verapdf:pdf-modelwcag-validation/pom.xml
Mavenorg.verapdf:corewcag-validation/pom.xml
Mavenorg.verapdf:wcag-algorithms${verapdf.wcag.algs.version}wcag-validation/pom.xml
All dependencies 19

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

RegistryPackageVersionRelation
Mavencom.sun.xml.bind:jaxb-core2.3.0.1direct
Mavencom.sun.xml.bind:jaxb-impl2.3.2direct
Mavenjavax.xml.bind:jaxb-api2.3.1direct
Mavenorg.verapdf:coredirect
Mavenorg.verapdf:feature-reporting1.31.0-SNAPSHOTdirect
Mavenorg.verapdf:metadata-fixer1.31.0-SNAPSHOTdirect
Mavenorg.verapdf:parserdirect
Mavenorg.verapdf:pdf-modeldirect
Mavenorg.verapdf:verapdf-xmp-coredirect
Mavenorg.verapdf:wcag-algorithmsdirect
Mavenorg.verapdf:wcag-validation1.31.0-SNAPSHOTdirect
Mavenjunit:junit4.13.1indirect
Mavenorg.apache.maven.plugins:maven-compiler-pluginindirect
Mavenorg.apache.maven.plugins:maven-jar-pluginindirect
Mavenorg.apache.maven.plugins:maven-javadoc-pluginindirect
Mavenorg.apache.maven.plugins:maven-project-info-reports-pluginindirect
Mavenorg.apache.maven.plugins:maven-surefire-pluginindirect
Mavenorg.codehaus.mojo:versions-maven-pluginindirect
Mavenorg.jacoco:jacoco-maven-pluginindirect
Dependency advisories 2

Installing maven:org.verapdf:metadata-fixer@1.30.2 pulls in 15 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
com.fasterxml.jackson.core:jackson-core2.21.1indirecthigh13.2.1
com.fasterxml.jackson.core:jackson-databind2.21.1indirecthigh103.2.1

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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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