Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 11:47 UTC

digitorus / pdfsign

Add/verify Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in PDF (using pure Go)

GoBSD-2-Clause★ 170 stars⑂ 51 forkssince Jun 2022View on GitHub ↗

digitorus/pdfsign holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (51/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

78
overall / 100
Good

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.

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

Ownership

DigitorusOrganization · verified domain
22 followers14 public repossince Jun 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/digitorus/pdfsignv0.9.0-674 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
8.3/36Commit cadence — 12/52 weeks with commits
18/18Commit volume — 149 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year149
human_commit_share0.92
days_since_last_push5
active_weeks_last_year12

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 6 releases published
36/36Release recency — latest release 12 days ago
27/27Release cadence — a release every ~12.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count6
latest_release_tagv1.0.0-rc5
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases12.2
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?

51Moderate · 17% of overall
How it's scored
36.1/60Stars — 170 stars
14.2/25Forks — 51 forks
1.7/15Watchers — 3 watchers
Inputs used
forks51
stars170
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, goreportcard.com, pkg.go.dev
has_pull_request_templateno

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.6/22.5Commit distribution — top contributor authored 62% of commits
10.8/13.5Contributor breadth — 8 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.62
How it's scored
36.8/42Issue resolution — 88% of issues closed
18.4/30PR acceptance — 84/137 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/9 approved changesets -- score normalized to 0
Inputs used
merged_prs84
open_issues5
closed_issues35
prs_merged_7d0
prs_decided_7d0
prs_merged_30d10
prs_decided_30d12
issue_closed_ratio0.875
closed_unmerged_prs53
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
9.8/25Owner reach — 22 followers of digitorus
20.6/25Track record — 14 public repos, account ~10 yr old
Inputs used
followers22
owner_typeOrganization
is_verifiedyes
owner_logindigitorus
public_repos14
account_age_days3,783

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 74 days ago
20/20Version history — 6 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/digitorus/pdfsign
ecosystemsgo
any_deprecatedno
min_days_since_publish74

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
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
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 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

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsgo, golang, pades, pdf, signing, esignature, signature, eseal, advanced-electronic-signature, aes, qes, qualified-electronic-signature
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 9 out of 9 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
0/7.5Code-Review — Found 0/9 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 9 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
2.2/7.5Vulnerabilities — 7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
23.1/35Direct dependencies free of known advisories — 3 affected: golang.org/x/crypto v0.56.0 (unknown), golang.org/x/crypto v0.57.0 (unknown), golang.org/x/text v0.40.0 (unknown)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
34.8/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 103 days ago
Inputs used
sourceosv
advisories13
affected_packages5
assessed_packages38
unassessed_packages0
affected_by_severityunknown 5
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 38 resolved dependencies against OSV. 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.

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.

68Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 81 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.88
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — go.mod, signers/aws/go.mod, signers/azure/go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — devcontainer, Dockerfile, lockfile
10/10Demonstrated agent practice — 27 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 8 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontaineryes
has_linter_configno
typecheck_configs—
agent_commit_share0.27
toolchain_manifestsgo.mod, signers/aws/go.mod, signers/azure/go.mod, signers/csc/go.mod, signers/gcp/go.mod, signers/pkcs11/go.mod
dependency_bot_commit_share0.08
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/140 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes41,251
source_files_sampled140
oversized_source_files0

Key facts

170GitHub stars
8contributors
149commits, last 12 months
5days since last push
6releases
1bus factor
5open issues
Gopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 51 ⇿
0Stars
51Forks
3Releases

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.

010203040504922023-012024-112026-09
Major 0Minor 1Patch 0

Each point covers 4 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-10-19 11:46 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests9 out of 9 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 0/9 approved changesets -- score normalized to 0
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
8SASTSAST tool is not run on all commits -- score normalized to 8
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Gogithub.com/digitorus/pdfv0.3.0go.mod
Gogithub.com/digitorus/pkcs7v0.0.0-20260914070511-d678ea5ea03fgo.mod
Gogithub.com/digitorus/timestampv0.0.0-20250524132541-c45532741eeago.mod
Gogithub.com/mattetti/filebufferv1.0.1go.mod
Gogolang.org/x/cryptov0.57.0go.mod
Gogolang.org/x/imagev0.46.0go.mod
Gogolang.org/x/textv0.42.0go.mod
All dependencies 38

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

RegistryPackageVersionRelation
Gogithub.com/digitorus/pdfv0.3.0direct
Gogithub.com/digitorus/pkcs7v0.0.0-20260914070511-d678ea5ea03fdirect
Gogithub.com/digitorus/timestampv0.0.0-20250524132541-c45532741eeadirect
Gogithub.com/mattetti/filebufferv1.0.1direct
Gogolang.org/x/cryptov0.56.0direct
Gogolang.org/x/cryptov0.57.0direct
Gogolang.org/x/imagev0.46.0direct
Gogolang.org/x/textv0.40.0direct
Gogolang.org/x/textv0.41.0direct
Gogolang.org/x/textv0.42.0direct
Gocloud.google.com/go/kmsv1.33.0indirect
Gocloud.google.com/go/longrunningv1.2.0indirect
Gogithub.com/aws/aws-sdk-go-v2v1.43.4indirect
Gogithub.com/aws/aws-sdk-go-v2/internal/configsourcesv1.4.35indirect
Gogithub.com/aws/aws-sdk-go-v2/internal/endpoints/v2v2.7.35indirect
Gogithub.com/aws/aws-sdk-go-v2/service/kmsv1.55.4indirect
Gogithub.com/aws/smithy-gov1.27.6indirect
Gogithub.com/azure/azure-sdk-for-go/sdk/azcorev1.22.0indirect
Gogithub.com/azure/azure-sdk-for-go/sdk/internalv1.12.0indirect
Gogithub.com/azure/azure-sdk-for-go/sdk/security/keyvault/azkeysv1.5.0indirect
Gogithub.com/azure/azure-sdk-for-go/sdk/security/keyvault/internalv1.2.0indirect
Gogithub.com/cespare/xxhash/v2v2.3.0indirect
Gogithub.com/go-logr/logrv1.4.4indirect
Gogithub.com/go-logr/stdrv1.2.2indirect
Gogithub.com/googleapis/gax-go/v2v2.23.0indirect
Gogithub.com/miekg/pkcs11v1.1.2indirect
Gogo.opentelemetry.io/auto/sdkv1.2.1indirect
Gogo.opentelemetry.io/otelv1.45.0indirect
Gogo.opentelemetry.io/otel/metricv1.45.0indirect
Gogo.opentelemetry.io/otel/tracev1.45.0indirect
Gogolang.org/x/netv0.57.0indirect
Gogolang.org/x/netv0.58.0indirect
Gogolang.org/x/sysv0.47.0indirect
Gogoogle.golang.org/apiv0.292.0indirect
Gogoogle.golang.org/genproto/googleapis/apiv0.0.0-20260803160001-6ac0973c030dindirect
Gogoogle.golang.org/genproto/googleapis/rpcv0.0.0-20260803160001-6ac0973c030dindirect
Gogoogle.golang.org/grpcv1.83.2indirect
Gogoogle.golang.org/protobufv1.36.11indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 38 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 3 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/cryptov0.56.0directunknown1—
golang.org/x/cryptov0.57.0directunknown1—
golang.org/x/textv0.40.0directunknown10.41.0
golang.org/x/netv0.57.0indirectunknown51.27.2
golang.org/x/netv0.58.0indirectunknown51.27.2

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

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go.