Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 01:01 UTC

surenkov / django-pydantic-field

Type-Safe Pydantic Schemas for Django JSONFields

PythonCustom license★ 219 stars⑂ 18 forkssince Jul 2022View on GitHub ↗
KindLibraryNetwork servicehow this is determined

surenkov/django-pydantic-field holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (88/100) and lowest on Security (38/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Savva SurenkovPersonal account
56 followers25 public repossince Jul 2011AgVend

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
PyPIdjango-pydantic-field0.5.62,259,483710 days agodjangopydanticjsonschema

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
15.3/18Commit volume — 49 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year49
human_commit_share1
days_since_last_push0
active_weeks_last_year8

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 62 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~34.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count62
latest_release_tagv0.5.6
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases34.7
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?

61Moderate · 17% of overall
How it's scored
37.9/60Stars — 219 stars
10.3/25Forks — 18 forks
3.3/15Watchers — 5 watchers
Inputs used
forks18
stars219
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license 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_licenseyes
readme_badges5
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 downloads — 2,259,483 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdjango-pydantic-field
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,259,483
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.4/22.5Commit distribution — top contributor authored 94% of commits
13.5/13.5Contributor breadth — 12 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.937
How it's scored
27.7/42Issue resolution — 66% of issues closed
28.5/30PR acceptance — 56/59 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/22 approved changesets -- score normalized to 0
Inputs used
merged_prs56
open_issues16
closed_issues31
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.66
closed_unmerged_prs3
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
12.6/25Owner reach — 56 followers of surenkov
22.3/25Track record — 25 public repos, account ~15 yr old
Inputs used
followers56
owner_typeUser
is_verified—
owner_loginsurenkov
public_repos25
account_age_days5,565
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 — 71 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdjango-pydantic-field
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://pypi.org/project/django-pydantic-field/
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsdjango, pydantic, jsonfield, schema
has_wikiyes
homepagehttps://pypi.org/project/django-pydantic-field/
docs_sitehttps://pypi.org/project/django-pydantic-field/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

38Weak · 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/2.5CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 2/22 approved changesets -- score normalized to 0
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.2/2.5License — license file detected
3.8/7.5Maintained — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
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
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 57 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
6.1/35Direct dependencies free of known advisories — 2 affected: django 5.2.9 (critical 9.8), django 6.0 (critical 9.8)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
26.8/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 260 days ago
Inputs used
sourceosv
advisories159
affected_packages12
assessed_packages50
unassessed_packages0
affected_by_severitycritical 2, high 4, moderate 5, low 1
direct_affected_packages2
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 50 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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.7/40Legible commit history — 37 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.37
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — src/django_pydantic_field/py.typed
10/10Reproducible environment — lockfile
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
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/django_pydantic_field/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/django_pydantic_field/py.typed)
55/55Manageable file sizes — 0/72 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes12,905
source_files_sampled72
oversized_source_files0

Key facts

219GitHub stars
12contributors
49commits, last 12 months
0days since last push
62releases
1bus factor
16open 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:django-pydantic-field@0.5.6; advisories assessed against the repository dependency graph instead

More detail

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

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.

0481216201812023-022024-122026-10
Major 0Minor 3Patch 32

Each point covers 4 days.

OpenSSF Scorecard 3.6 / 10
3.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-10-22 01:01 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/22 approved changesets -- score normalized to 0
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
9Licenselicense file detected
5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
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
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities57 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPIpydantic>=1.10,<3pyproject.toml
PyPIdjango>=3.1pyproject.toml
PyPItyping_extensions—pyproject.toml
All dependencies 50

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

RegistryPackageVersionRelation
PyPIdjango5.2.9direct
PyPIdjango6.0direct
PyPIpydantic2.14.1direct
PyPItyping-extensions4.16.0direct
PyPIannotated-types0.7.0indirect
PyPIasgiref3.11.0indirect
PyPIcertifi2026.1.4indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.4indirect
PyPIcolorama0.4.6indirect
PyPIdistlib0.4.0indirect
PyPIdj-database-url2.3.0indirect
PyPIdjango-jsonform2.23.2indirect
PyPIdjango-pydantic-field0.5.6indirect
PyPIdjango-stubs5.2.8indirect
PyPIdjango-stubs-ext5.2.8indirect
PyPIdjangorestframework3.16.1indirect
PyPIdjangorestframework-stubs3.16.6indirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock3.20.2indirect
PyPIidentify2.6.15indirect
PyPIidna3.11indirect
PyPIinflection0.5.1indirect
PyPIiniconfig2.3.0indirect
PyPImysqlclient2.3.0indirect
PyPInodeenv1.10.0indirect
PyPIpackaging25.0indirect
PyPIplatformdirs4.5.1indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.5.1indirect
PyPIpsycopg3.3.6indirect
PyPIpsycopg-binary3.3.6indirect
PyPIpydantic-core2.50.1indirect
PyPIpygments2.19.2indirect
PyPIpytest9.0.2indirect
PyPIpytest-django4.11.1indirect
PyPIpyyaml6.0.3indirect
PyPIrequests2.32.5indirect
PyPIruff0.14.10indirect
PyPIsqlparse0.5.5indirect
PyPIsyrupy5.0.0indirect
PyPItomli2.3.0indirect
PyPIty0.0.16indirect
PyPItypes-pyyaml6.0.12.20250915indirect
PyPItypes-requests2.32.4.20250913indirect
PyPItyping-inspection0.4.4indirect
PyPItzdata2025.3indirect
PyPIuritemplate4.2.0indirect
PyPIurllib32.6.2indirect
PyPIvirtualenv20.35.4indirect
Dependency advisories 12

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

PackageVersionRelationSeverityAdvisoriesFixed in
django5.2.9directcritical526.1.1
django6.0directcritical526.1.1
certifi2026.1.4indirecthigh22026.10.19
sqlparse0.5.5indirecthigh100.6.0
urllib32.6.2indirecthigh122.8.0
virtualenv20.35.4indirecthigh1721.14.9
djangorestframework3.16.1indirectmoderate43.17.2
filelock3.20.2indirectmoderate23.20.3
idna3.11indirectmoderate23.15
pytest9.0.2indirectmoderate29.0.3
requests2.32.5indirectmoderate22.33.0
pygments2.19.2indirectlow22.20.0

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.