Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 06:40 UTC

pydantic / speedate

Fast and simple datetime, date, time and duration parsing for rust.

RustMIT★ 254 stars⑂ 29 forkssince May 2022View on GitHub ↗

pydantic/speedate holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (76/100) and lowest on Community & Adoption (65/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

PydanticOrganization · verified domain
3,124 followers90 public repossince Aug 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iospeedate0.18.01,533,093262 days agodatedatetimeiso8601rfc3339timedate-and-timeparsing

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
4.8/36Commit cadence — 7/52 weeks with commits
10.3/18Commit volume — 13 commits in the last year
6/10OpenSSF Scorecard: Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year13
human_commit_share0.9
days_since_last_push2
active_weeks_last_year7
How it's scored
27/27Ships releases — 25 releases published
36/36Release recency — latest release 2 days ago
19.8/27Release cadence — a release every ~119.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count25
latest_release_tagv0.18.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases119.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?

65Good · 17% of overall
How it's scored
39/60Stars — 254 stars
12.1/25Forks — 29 forks
5/15Watchers — 9 watchers
Inputs used
forks29
stars254
watchers9
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 1,533,093 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesspeedate
dependents—
ecosystemscrates
total_downloads14,040,303
monthly_downloads1,533,093
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?

75Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.7/22.5Commit distribution — top contributor authored 61% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.613
How it's scored
31.5/42Issue resolution — 75% of issues closed
26.3/30PR acceptance — 72/82 decided PRs merged
10.4/13Newcomer PR acceptance — 4/5 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 8/22 approved changesets -- score normalized to 3
Inputs used
merged_prs72
open_issues7
closed_issues21
prs_merged_7d4
prs_decided_7d5
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.75
closed_unmerged_prs10
first_time_authors_30d2
first_time_prs_merged_30d4
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 3,124 followers of pydantic
21.4/25Track record — 90 public repos, account ~4 yr old
Inputs used
followers3,124
owner_typeOrganization
is_verifiedyes
owner_loginpydantic
public_repos90
account_age_days1,531

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 2 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesspeedate
ecosystemscrates
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .rustfmt.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 16 out of 30 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/speedate/latest/speedate/
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsiso8601, rfc3339, date, parser, pydantic, rust, datetime, parse, time, timezone
has_wikino
homepagehttps://docs.rs/speedate/latest/speedate/
docs_sitehttps://docs.rs/speedate/latest/speedate/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.2/2.5CI-Tests — 16 out of 30 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 8/22 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 12 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
4.5/7.5Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
5/5Packaging — packaging workflow detected
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.6
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
26.6/35Direct dependencies free of known advisories — 1 affected: paste 1.0.15 (unknown)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
37.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 740 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages48
unassessed_packages0
affected_by_severityunknown 1
direct_affected_packages1
Matched the crates:speedate@0.18.0 runtime dependency closure — what installing the published package pulls in — 48 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35/40Legible commit history — 59 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.656
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .rustfmt.toml
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, fuzz/Cargo.toml
dependency_bot_commit_share0.1
How it's scored
45/45Type-checkable code — Rust (statically typed)
51.3/55Manageable file sizes — 1/15 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes63,547
source_files_sampled15
oversized_source_files1

Key facts

254GitHub stars
18contributors
13commits, last 12 months
2days since last push
25releases
1bus factor
7open issues
crates.iopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 29 ⇿
0Stars
29Forks
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.

0510152025302922022-062024-082026-10
Major 0Minor 13Patch 6

Each point covers 4 days.

OpenSSF Scorecard 6.6 / 10
6.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-18 06:40 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
5CI-Tests16 out of 30 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 8/22 approved changesets -- score normalized to 3
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
crates.ioarrayvec0.7.8Cargo.toml
crates.iolexical-parse-float1.0.6Cargo.toml
crates.iostrum0.28Cargo.toml
crates.iostrum_macros0.28Cargo.toml
All dependencies 31

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

RegistryPackageVersionRelation
crates.ioarrayvec—direct
crates.iolexical-parse-float—direct
crates.iostrum—direct
crates.iostrum0.24.0direct
crates.iostrum_macros—direct
crates.iostrum_macros0.24.0direct
crates.ioarbitrary1.1.0indirect
crates.ioautocfg1.1.0indirect
crates.iocc1.0.73indirect
crates.iochrono—indirect
crates.iochrono0.4.19indirect
crates.ioheck0.4.0indirect
crates.ioiso8601—indirect
crates.iolibc0.2.126indirect
crates.iolibfuzzer-sys0.4.3indirect
crates.ionum-integer0.1.45indirect
crates.ionum-traits0.2.15indirect
crates.ioonce_cell1.12.0indirect
crates.iopaste—indirect
crates.ioproc-macro21.0.39indirect
crates.ioquote1.0.18indirect
crates.iorustversion1.0.6indirect
crates.iospeedate0.7.0indirect
crates.iospeedate-fuzz0.0.0indirect
crates.iosyn1.0.96indirect
crates.iotime0.1.44indirect
crates.iounicode-ident1.0.0indirect
crates.iowasi0.10.0+wasi-snapshot-preview1indirect
crates.iowinapi0.3.9indirect
crates.iowinapi-i686-pc-windows-gnu0.4.0indirect
crates.iowinapi-x86_64-pc-windows-gnu0.4.0indirect
Dependency advisories 1

Installing crates:speedate@0.18.0 pulls in 48 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
paste1.0.15directunknown1—

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 — crates.io.