Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 13:55 UTC

pydot / pydot

Python interface to Graphviz's Dot language

PythonCustom license★ 1,000 stars⑂ 176 forkssince Apr 2015View on GitHub ↗

pydot/pydot holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Security (77/100) and lowest on AI Readiness (56/100). It was last updated 4 days ago. 2 contributors account for most of its recent work.

81
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.

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

Ownership

pydotOrganization
12 followers2 public repossince Feb 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpydot4.0.123,155,68819435 days agographvizdotgraphsvisualization

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
15.2/36Commit cadence22/52 weeks with commits
15.2/18Commit volume48 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year48
human_commit_share0.68
days_since_last_push4
active_weeks_last_year22
How it's scored
16.2/27Ships releases19 version tags (no GitHub releases)
7.2/36Release recencylatest release 435 days ago
12.6/27Release cadencea release every ~264.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count19
latest_release_tagv4.0.1
releases_from_tagsyes
days_since_latest_release435
mean_days_between_releases264.3
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?

70Good · 17% of overall
How it's scored
48.7/60Stars1,000 stars
18.7/25Forks176 forks
7.4/15Watchers22 watchers
Inputs used
forks176
stars1,000
watchers22
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
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads23,155,688 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespydot
dependents
ecosystemspypi
total_downloads
monthly_downloads23,155,688
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?

66Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.9/22.5Commit distributiontop contributor authored 34% of commits
13.5/13.5Contributor breadth35 contributors
10/10OpenSSF Scorecard: Contributorsproject has 30 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled35
top_contributor_share0.337
How it's scored
36.5/42Issue resolution87% of issues closed
21.7/30PR acceptance205/284 decided PRs merged
9.8/13Newcomer PR acceptance3/4 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 7/22 approved changesets -- score normalized to 3
Inputs used
merged_prs205
open_issues37
closed_issues243
prs_merged_7d3
prs_decided_7d4
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.868
closed_unmerged_prs79
first_time_authors_30d2
first_time_prs_merged_30d3
first_time_prs_decided_30d4
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
8/25Owner reach12 followers of pydot
15.5/25Track record2 public repos, account ~11 yr old
Inputs used
followers12
owner_typeOrganization
is_verifiedno
owner_loginpydot
public_repos2
account_age_days4,201
How it's scored
25/25Published & resolvable1 package(s) on pypi
14/35Publish recencylatest publish 435 days ago
20/20Version history19 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespydot
ecosystemspypi
any_deprecatedno
min_days_since_publish435

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests24 out of 24 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pypi.python.org/pypi/pydot
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicspython, graphviz, dot-language, hacktoberfest
has_wikino
homepagehttps://pypi.python.org/pypi/pydot
docs_sitehttps://pypi.python.org/pypi/pydot
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

77Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0.5/2.5CII-Best-Practicesbadge detected: InProgress
2.2/7.5Code-ReviewFound 7/22 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 30 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.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
4.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file 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_aggregate7.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:pydot@4.0.1 runtime dependency closure — what installing the published package pulls in — 1 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history53 of 68 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.779
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingsrc/pydot/py.typed
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance32 of the last 100 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configssrc/pydot/py.typed
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.32
How it's scored
27/45Type-checkable codePython with type-check config (src/pydot/py.typed)
55/55Manageable file sizes0/16 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes59,412
source_files_sampled16
oversized_source_files0

Key facts

1,000GitHub stars
35contributors
48commits, last 12 months
4days since last push
19releases
2bus factor
37open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 176 ⇿
0Stars
176Forks
19Releases

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.

0408012016020017132015-042020-122026-08
Major 3Minor 4Patch 12

Each point covers 11 days.

OpenSSF Scorecard 7.1 / 10
7.1aggregate

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-08-27 13:55 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
2CII-Best-Practicesbadge detected: InProgress
3Code-ReviewFound 7/22 approved changesets -- score normalized to 3
10Contributorsproject has 30 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIpyparsing>=3.1.0pyproject.toml
All dependencies 2

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

RegistryPackageVersionRelation
PyPIpyparsingdirect
PyPIsetuptoolsindirect
Dependency advisories 0

Installing pypi:pydot@4.0.1 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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 statisticsPyPI.