Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 14:47 UTC

dapper91 / pydantic-xml

python xml for humans

PythonUnlicense★ 258 stars⑂ 37 forkssince Apr 2022View on GitHub ↗

dapper91/pydantic-xml holds a health index of 15 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (95/100) and lowest on Security (27/100). It was last updated today. A single contributor accounts for most of its recent work.

15
overall / 100
Critical

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.

15
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 66 is calibrated to 77 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 20% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Dmitry PershinPersonal account
19 followers36 public repossince Sep 2012Tochka Bank

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpydantic-xml2.22.02,484,833570 days agopydanticxmlserializationdeserializationlxml

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
3.5/36Commit cadence — 5/52 weeks with commits
13.5/18Commit volume — 31 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year31
human_commit_share1
days_since_last_push0
active_weeks_last_year5
How it's scored
27/27Ships releases — 57 releases published
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~57.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count57
latest_release_tagv2.22.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases57.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?

64Moderate · 17% of overall
How it's scored
39.1/60Stars — 258 stars
13/25Forks — 37 forks
1.7/15Watchers — 3 watchers
Inputs used
forks37
stars258
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Unlicense)
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, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 2,484,833 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespydantic-xml
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,484,833
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.8/22.5Commit distribution — top contributor authored 96% of commits
13.5/13.5Contributor breadth — 11 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.965
How it's scored
36.5/42Issue resolution — 87% of issues closed
27.3/30PR acceptance — 159/175 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/15 approved changesets -- score normalized to 1
Inputs used
merged_prs159
open_issues20
closed_issues133
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.869
closed_unmerged_prs16
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9.4/25Owner reach — 19 followers of dapper91
23.4/25Track record — 36 public repos, account ~14 yr old
Inputs used
followers19
owner_typeUser
is_verified—
owner_logindapper91
public_repos36
account_age_days5,141
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 57 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespydantic-xml
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

95Exceptional · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .flake8
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 14 out of 15 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://pydantic-xml.readthedocs.io
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsdeserialization, lxml, parser, pydantic, python, serialization, xml
has_wikiyes
homepagehttps://pydantic-xml.readthedocs.io
docs_sitehttps://pydantic-xml.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

27At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 14 out of 15 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/15 approved changesets -- score normalized to 1
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
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
0/5Security-Policy — security policy file not 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier20
security_posture_after_multiplier9
security_posture_before_jurisdiction44
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 20% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages59
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 59 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
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.pydantic.dev/llms.txt)
36.8/40Legible commit history — 69 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.pydantic.dev/llms.txt
legible_history_share0.69
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — .flake8
11/11Static type checking — pydantic_xml/py.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_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configspydantic_xml/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (pydantic_xml/py.typed)
55/55Manageable file sizes — 0/107 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes18,929
source_files_sampled107
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

258GitHub stars
11contributors
31commits, last 12 months
0days since last push
57releases
1bus factor
20open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:pydantic-xml@2.22.0; advisories assessed against the repository dependency graph instead

More detail

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

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.

01325383722022-122024-112026-10
Major 2Minor 25Patch 19

Each point covers 4 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-18 14:46 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests14 out of 15 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/15 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
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
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 8
RegistryPackageVersion constraintManifest
PyPIlxml>=4.9.0pyproject.toml
PyPIpydantic>=2.14.0pyproject.toml
PyPIpydantic-core>=2.15.0pyproject.toml
PyPIfuro^2022.12.7pyproject.toml
PyPISphinx^5.3.0pyproject.toml
PyPIsphinx-copybutton^0.5.1pyproject.toml
PyPIsphinx_design^0.3.0pyproject.toml
PyPItoml^0.10.2pyproject.toml
All dependencies 59

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

RegistryPackageVersionRelation
PyPIfuro2022.12.7direct
PyPIlxml6.1.3direct
PyPIpydantic2.14.1direct
PyPIpydantic-core2.50.1direct
PyPIsphinx5.3.0direct
PyPIsphinx-copybutton0.5.2direct
PyPIsphinx-design0.3.0direct
PyPItoml0.10.2direct
PyPIalabaster0.7.16indirect
PyPIannotated-types0.8.0indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIcertifi2026.7.22indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.2indirect
PyPIdistlib0.4.4indirect
PyPIdocutils0.19indirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock4.1.0indirect
PyPIidentify2.6.20indirect
PyPIidna3.20indirect
PyPIimagesize2.0.1indirect
PyPIiniconfig2.3.1indirect
PyPIjinja23.1.6indirect
PyPIlibrt0.16.0indirect
PyPIlxml-stubs0.5.1indirect
PyPImarkupsafe3.0.4indirect
PyPImypy1.20.2indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.11.0indirect
PyPIpackaging26.3indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.12.4indirect
PyPIpluggy1.7.0indirect
PyPIpre-commit3.2.2indirect
PyPIpygments2.21.0indirect
PyPIpytest7.4.4indirect
PyPIpytest-cov4.1.0indirect
PyPIpython-discovery1.6.3indirect
PyPIpyyaml6.0.3indirect
PyPIrequests2.34.2indirect
PyPIsetuptools84.0.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsoupsieve2.10indirect
PyPIsphinx-basic-ng1.0.0b2indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItomli2.5.0indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib32.8.0indirect
PyPIvirtualenv21.14.11indirect
PyPIxmldiff2.7.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
pytest7.4.4indirectmoderate29.0.3

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 — PyPI.