Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-08 20:14 UTC

dj-bolt / django-bolt

Rust-powered API framework for Django achieving 60k+ RPS. Uses Actix Web for HTTP, PyO3 for Python bridging, msgspec for serialization. Decorator-based routing with built-in auth and middleware.

Python · RustNo license detected★ 1,606 stars⑂ 83 forkssince Sep 2025View on GitHub ↗
KindLibraryCommand-line toolNetwork servicePluginMCP serverhow this is determined

dj-bolt/django-bolt holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Security (54/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

dj-boltOrganization
11 followers1 public reposince Feb 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIdjango-bolt0.10.0-620 days agodjangoapirustperformanceactixpyo3async

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
29.1/36Commit cadence42/52 weeks with commits
18/18Commit volume456 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year456
human_commit_share1
days_since_last_push0
active_weeks_last_year42
How it's scored
27/27Ships releases61 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~10.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count61
latest_release_tagv0.10.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases10.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

55Moderate · 17% of overall
How it's scored
52/60Stars1,606 stars
16/25Forks83 forks
7.7/15Watchers25 watchers
Inputs used
forks83
stars1,606
watchers25
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesopencollective.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.8/22.5Commit distributiontop contributor authored 88% of commits
13.5/13.5Contributor breadth27 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled27
top_contributor_share0.877
How it's scored
40.8/42Issue resolution97% of issues closed
24.6/30PR acceptance128/156 decided PRs merged
6.5/13Newcomer PR acceptance1/2 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/30 approved changesets -- score normalized to 1
Inputs used
merged_prs128
open_issues3
closed_issues99
prs_merged_7d2
prs_decided_7d2
prs_merged_30d11
prs_decided_30d12
issue_closed_ratio0.971
closed_unmerged_prs28
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
7.8/25Owner reach11 followers of dj-bolt
3.2/25Track record1 public repos, account ~0 yr old
Inputs used
followers11
owner_typeOrganization
is_verified
owner_logindj-bolt
public_repos1
account_age_days175
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history62 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdjango-bolt
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics11 topics
10/10Wiki
Inputs used
topicsactix-web, api, api-rest, asyncio, bolt, django, msgspec, pyo3, python, rust, django-bolt
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/30 approved changesets -- score normalized to 1
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

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.

70Good · 4% of overall
How it's scored
45/45Agent instructionsAgents.md, CLAUDE.md, src/Claude.md
0/15Machine-readable docs (llms.txt)
37.3/40Legible commit history70 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.7
agent_instruction_filesAgents.md, CLAUDE.md, src/Claude.md
agent_instruction_max_bytes41,040
How it's scored
18/18One-command bootstrapjustfile
22/22Automated tests
11/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, uv.lock
has_dockerfileno
typed_languageno
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
54.2/55Manageable file sizes7/494 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes146,032
source_files_sampled494
oversized_source_files7
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examplesexample, examples
Inputs used
example_dirsexample, examples
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

1,606GitHub stars
27contributors
456commits, last 12 months
0days since last push
61releases
1bus factor
3open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'django-bolt' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:django-bolt@0.10.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 83 ⇿
0Stars
83Forks
57Releases

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.

0204060801008332025-102026-032026-08
Major 0Minor 7Patch 48
OpenSSF Scorecard 5.4 / 10
5.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-08-08 20:13 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/30 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 51
RegistryPackageVersion constraintManifest
crates.iopyo30.29Cargo.toml
crates.iopyo3-async-runtimes0.29Cargo.toml
crates.ioactix-web4Cargo.toml
crates.ioactix-http3Cargo.toml
crates.ioactix-web-actors4Cargo.toml
crates.ioactix0.13Cargo.toml
crates.ioactix-files0.6Cargo.toml
crates.iotokio1Cargo.toml
crates.iosocket20.6Cargo.toml
crates.iomatchit0.9Cargo.toml
crates.iogovernor0.10Cargo.toml
crates.iojsonwebtoken10Cargo.toml
crates.iobase640.22Cargo.toml
crates.iodashmap6Cargo.toml
crates.ioparking_lot0.12Cargo.toml
crates.ioserde1Cargo.toml
crates.ioserde_json1Cargo.toml
crates.ioahash0.8Cargo.toml
crates.iomimalloc0.1Cargo.toml
crates.iotikv-jemallocator0.6Cargo.toml
crates.iourlencoding2Cargo.toml
crates.ioonce_cell1Cargo.toml
crates.iofutures-util0.3Cargo.toml
crates.iobytes1Cargo.toml
crates.iobrotli8Cargo.toml
crates.ioflate21Cargo.toml
crates.iozstd0.13Cargo.toml
crates.ioregex1Cargo.toml
crates.iochrono0.4Cargo.toml
crates.iouuid1Cargo.toml
crates.ioactix-multipart0.7Cargo.toml
crates.ioserde_urlencoded0.7Cargo.toml
crates.iotempfile3Cargo.toml
crates.iolog0.4Cargo.toml
crates.ionotify8Cargo.toml
crates.ioctrlc3Cargo.toml
crates.iolibc0.2Cargo.toml
crates.iormcp3.1.2Cargo.toml
crates.iohttp1Cargo.toml
crates.iohttp-body1Cargo.toml
crates.iohttp-body-util0.1Cargo.toml
crates.iotokio-util0.7Cargo.toml
crates.iosha20.10Cargo.toml
PyPIDjango>=4.2pyproject.toml
PyPIclick>=8.1pyproject.toml
PyPIhttpx>=0.28.1pyproject.toml
PyPImsgspec>=0.20pyproject.toml
PyPIpyjwt>=2.10.1pyproject.toml
PyPItyping-extensions>=4.5.0pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIuvloop>=0.22.1pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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

How one result sits in the wider record: aggregate statisticsPyPI.