Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 15:30 UTC

erdem / django-map-widgets

Highly customizable, intuitive, and user-friendly map widgets for GeoDjango applications.

JavaScript · Python · HTMLMIT★ 470 stars⑂ 125 forkssince Feb 2016View on GitHub ↗
KindLibraryNetwork servicehow this is determined

erdem/django-map-widgets holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on AI Readiness (34/100). It was last updated 41 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Erdem OzkolPersonal account
218 followers35 public repossince Mar 2012

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-map-widgets0.6.0124,2712453 days agodjangomap-widgetsgeodjangogeolocationmapboxgooglemapleafletinteractive-maps
PyPIdemopoints to another repo — not scored0.1.0615630 days agotestegg

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
18/36Push recency — last push 41 days ago
4.2/36Commit cadence — 6/52 weeks with commits
12.2/18Commit volume — 22 commits in the last year
10/10OpenSSF Scorecard: Maintained — 14 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year22
human_commit_share1
days_since_last_push41
active_weeks_last_year6
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 53 days ago
12.6/27Release cadence — a release every ~181.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv0.6.0
releases_from_tagsno
days_since_latest_release53
mean_days_between_releases181.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?

66Good · 17% of overall
How it's scored
43.3/60Stars — 470 stars
17.4/25Forks — 125 forks
7/15Watchers — 19 watchers
Inputs used
forks125
stars470
watchers19
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
67.9/80Monthly downloads — 124,271 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdjango-map-widgets
dependents—
ecosystemspypi
total_downloads—
monthly_downloads124,271
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.4/22.5Commit distribution — top contributor authored 89% of commits
13.5/13.5Contributor breadth — 32 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled32
top_contributor_share0.894
How it's scored
42/42Issue resolution — 100% of issues closed
21.5/30PR acceptance — 56/78 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/30 approved changesets -- score normalized to 0
Inputs used
merged_prs56
open_issues0
closed_issues90
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs22
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
16.8/25Owner reach — 218 followers of erdem
23.3/25Track record — 35 public repos, account ~14 yr old
Inputs used
followers218
owner_typeUser
is_verified—
owner_loginerdem
public_repos35
account_age_days5,299
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 53 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdjango-map-widgets
ecosystemspypi
any_deprecatedno
min_days_since_publish53

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
16/16Linter config — pyproject.toml ([tool.black], [tool.isort])
9.6/9.6Pre-commit hooks
0/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_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://django-map-widgets.readthedocs.io/
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsdjango-map-widgets, django-admin, map-widgets, django, geolocation, geospatial, geodjango
has_wikiyes
homepage—
docs_sitehttps://django-map-widgets.readthedocs.io/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

36Weak · 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/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
7.5/7.5Maintained — 14 commit(s) and 2 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
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
0/7.5Vulnerabilities — 46 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
7.6/35Direct dependencies free of known advisories — 1 affected: django 5.2.12 (critical 9.8)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
32.1/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 157 days ago
Inputs used
sourceosv
advisories88
affected_packages13
assessed_packages62
unassessed_packages2
affected_by_severitycritical 3, high 6, moderate 3, low 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 62 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.5/40Legible commit history — 31 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.31
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
0/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.black], [tool.isort])
0/11Static type checking
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_testsno
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
53.5/55Manageable file sizes — 2/73 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes70,263
source_files_sampled73
oversized_source_files2

Key facts

470GitHub stars
32contributors
22commits, last 12 months
41days since last push
16releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'django-map-widgets' from its registry
  • pypi package 'demo' points at a different repository (UNKNOWN); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 125 ⇿
0Stars
125Forks
13Releases

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.

025507510012512132016-062021-062026-06
Major 0Minor 4Patch 9

Each point covers 10 days.

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-09-11 15:30 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/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 2 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities46 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmuglifycss0.0.27package.json
npmuglify-js~3.1.9package.json
PyPIdjango>=4.0,<7.0pyproject.toml
All dependencies 64

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

RegistryPackageVersionRelation
npmuglify-js~3.1.9direct
npmuglifycss0.0.27direct
PyPIdjango5.2.12direct
PyPIalabaster0.7.16indirect
PyPIasgiref3.11.1indirect
PyPIasttokens2.4.1indirect
PyPIbabel2.15.0indirect
PyPIblack24.4.2indirect
PyPIcertifi2024.6.2indirect
PyPIcfgv3.4.0indirect
PyPIcharset-normalizer3.3.2indirect
PyPIclick8.1.7indirect
PyPIcolorama0.4.6indirect
PyPIdecorator5.1.1indirect
PyPIdistlib0.3.8indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.3.1indirect
PyPIexecuting2.0.1indirect
PyPIfilelock3.15.4indirect
PyPIidentify2.5.36indirect
PyPIidna3.7indirect
PyPIimagesize1.4.1indirect
PyPIipdb0.13.13indirect
PyPIipython8.25.0indirect
PyPIisort5.13.2indirect
PyPIjedi0.19.1indirect
PyPIjinja23.1.4indirect
PyPImarkupsafe2.1.5indirect
PyPImatplotlib-inline0.1.7indirect
PyPImypy-extensions1.0.0indirect
PyPInodeenv1.9.1indirect
PyPIpackaging24.1indirect
PyPIparso0.8.4indirect
PyPIpathspec0.12.1indirect
PyPIpexpect4.9.0indirect
PyPIplatformdirs4.2.2indirect
PyPIpre-commit3.7.1indirect
PyPIprompt-toolkit3.0.47indirect
PyPIpsycopg2-binary2.9.12indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.2indirect
PyPIpygments2.18.0indirect
PyPIpyyaml6.0.1indirect
PyPIrequests2.32.3indirect
PyPIsetuptools70.1.0indirect
PyPIsix1.16.0indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsphinx7.3.7indirect
PyPIsphinx-rtd-theme—indirect
PyPIsphinxcontrib-applehelp1.0.8indirect
PyPIsphinxcontrib-devhelp1.0.6indirect
PyPIsphinxcontrib-htmlhelp2.0.5indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.7indirect
PyPIsphinxcontrib-serializinghtml1.1.10indirect
PyPIsqlparse0.5.0indirect
PyPIstack-data0.6.3indirect
PyPItomli2.4.1indirect
PyPItraitlets5.14.3indirect
PyPItyping-extensions4.15.0indirect
PyPItzdata2024.1indirect
PyPIurllib32.2.2indirect
PyPIvirtualenv20.26.3indirect
PyPIwcwidth0.2.13indirect
Dependency advisories 13

This repository publishes no package the index resolves, so its own dependency graph was assessed — 62 packages, which also include development and test pins that never ship: 13 carry known advisories, of which 1 are direct. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
django5.2.12directcritical336.0.8
black24.4.2indirectcritical326.3.1
virtualenv20.26.3indirectcritical420.36.1
certifi2024.6.2indirecthigh22024.7.4
click8.1.7indirecthigh18.3.3
jinja23.1.4indirecthigh63.1.6
setuptools70.1.0indirecthigh483.0.0
sqlparse0.5.0indirecthigh110.6.0
urllib32.2.2indirecthigh122.7.0
filelock3.15.4indirectmoderate43.20.3
idna3.7indirectmoderate23.15
requests2.32.3indirectmoderate42.33.0
pygments2.18.0indirectlow22.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.