Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 08:18 UTC

cesarb / constant_time_eq

Compares two equal-sized byte strings in constant time.

RustApache-2.0★ 48 stars⑂ 12 forkssince May 2015View on GitHub ↗

cesarb/constant_time_eq holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (62/100) and lowest on Security (21/100). It was last updated 17 days ago. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

Cesar Eduardo BarrosPersonal account
47 followers22 public repossince Oct 2008

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
crates.ioconstant_time_eq0.6.022,808,7462117 days agoconstant-timecryptographyno-std

Metrics by category

Vitality

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

56Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 17 days ago
2.1/36Commit cadence — 3/52 weeks with commits
10.6/18Commit volume — 14 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year14
human_commit_share1
days_since_last_push17
active_weeks_last_year3
How it's scored
16.2/27Ships releases — 21 version tags (no GitHub releases)
36/36Release recency — latest release 17 days ago
12.6/27Release cadence — a release every ~140.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count21
latest_release_tag0.6.0
releases_from_tagsyes
days_since_latest_release17
mean_days_between_releases140.9

Community & Adoption

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

58Moderate · 17% of overall
How it's scored
27.1/60Stars — 48 stars
8.7/25Forks — 12 forks
1.7/15Watchers — 3 watchers
Inputs used
forks12
stars48
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 22,808,746 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesconstant_time_eq
dependents—
ecosystemscrates
total_downloads316,295,445
monthly_downloads22,808,746
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1/22.5Commit distribution — top contributor authored 95% of commits
6.8/13.5Contributor breadth — 5 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.954
How it's scored
31.5/42Issue resolution — 75% of issues closed
20/30PR acceptance — 4/6 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs4
open_issues2
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.75
closed_unmerged_prs2
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
12.1/25Owner reach — 47 followers of cesarb
21.9/25Track record — 22 public repos, account ~17 yr old
Inputs used
followers47
owner_typeUser
is_verified—
owner_logincesarb
public_repos22
account_age_days6,533
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 crates
35/35Publish recency — latest publish 17 days ago
20/20Version history — 21 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesconstant_time_eq
ecosystemscrates
any_deprecatedno
min_days_since_publish17

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/constant_time_eq
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/constant_time_eq
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesCargo.lock
manifestsCargo.toml
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages54
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the crates:constant_time_eq@0.6.0 runtime dependency closure — what installing the published package pulls in — 54 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8/40Legible commit history — 15 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.15
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically 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 — no data
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/11 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes9,859
source_files_sampled11
oversized_source_files0

Key facts

48GitHub stars
5contributors
14commits, last 12 months
17days since last push
21releases
1bus factor
2open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/cesarb/constant_time_eq: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/cesarb/constant_time_eq/legacy.tar.gz/refs/heads/main": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 12 ⇿
0Stars
12Forks
14Releases

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.

0246810121112021-072023-122026-06
Major 0Minor 4Patch 10

Each point covers 5 days.

All dependencies 79

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

RegistryPackageVersionRelation
crates.ioaho-corasick1.1.5indirect
crates.ioalloca0.4.0indirect
crates.ioanes0.1.6indirect
crates.ioanstyle1.0.14indirect
crates.ioautocfg1.5.1indirect
crates.iobitflags2.13.1indirect
crates.iobumpalo3.20.3indirect
crates.iocast0.3.0indirect
crates.iocc1.4.4indirect
crates.iocfg-if1.0.4indirect
crates.iociborium0.2.2indirect
crates.iociborium-io0.2.2indirect
crates.iociborium-ll0.2.2indirect
crates.ioclap4.6.6indirect
crates.ioclap_builder4.6.6indirect
crates.ioclap_lex1.1.0indirect
crates.iocount_instructions0.2.1indirect
crates.iocriterion0.8.2indirect
crates.iocriterion-plot0.8.2indirect
crates.iocrossbeam-deque0.8.7indirect
crates.iocrossbeam-epoch0.9.20indirect
crates.iocrossbeam-utils0.8.22indirect
crates.iocrunchy0.2.4indirect
crates.ioeither1.18.0indirect
crates.ioerrno0.3.14indirect
crates.iofind-msvc-tools0.1.11indirect
crates.iofutures-core0.3.34indirect
crates.iofutures-task0.3.34indirect
crates.iofutures-util0.3.34indirect
crates.iohalf2.7.1indirect
crates.ioitertools0.13.0indirect
crates.ioitoa1.0.18indirect
crates.iojs-sys0.3.104indirect
crates.iolibc0.2.189indirect
crates.iolinux-raw-sys0.12.1indirect
crates.iomemchr2.8.3indirect
crates.ionum-traits0.2.19indirect
crates.ioonce_cell1.21.4indirect
crates.iooorandom11.1.5indirect
crates.iopage_size0.6.0indirect
crates.iopin-project-lite0.2.17indirect
crates.ioplotters0.3.7indirect
crates.ioplotters-backend0.3.7indirect
crates.ioplotters-svg0.3.7indirect
crates.ioproc-macro21.0.107indirect
crates.ioquote1.0.47indirect
crates.iorayon1.12.0indirect
crates.iorayon-core1.13.0indirect
crates.ioregex1.13.1indirect
crates.ioregex-automata0.4.18indirect
crates.ioregex-syntax0.8.11indirect
crates.iorustix1.1.4indirect
crates.iorustversion1.0.23indirect
crates.iosame-file1.0.6indirect
crates.ioserde1.0.229indirect
crates.ioserde_core1.0.229indirect
crates.ioserde_derive1.0.229indirect
crates.ioserde_json1.0.151indirect
crates.ioshlex2.0.1indirect
crates.ioslab0.4.12indirect
crates.iosyn2.0.119indirect
crates.iosyn3.0.4indirect
crates.iotinytemplate1.2.1indirect
crates.iounicode-ident1.0.24indirect
crates.iowalkdir2.5.0indirect
crates.iowasm-bindgen0.2.127indirect
crates.iowasm-bindgen-macro0.2.127indirect
crates.iowasm-bindgen-macro-support0.2.127indirect
crates.iowasm-bindgen-shared0.2.127indirect
crates.ioweb-sys0.3.104indirect
crates.iowinapi0.3.9indirect
crates.iowinapi-i686-pc-windows-gnu0.4.0indirect
crates.iowinapi-util0.1.11indirect
crates.iowinapi-x86_64-pc-windows-gnu0.4.0indirect
crates.iowindows-link0.2.1indirect
crates.iowindows-sys0.61.2indirect
crates.iozerocopy0.8.56indirect
crates.iozerocopy-derive0.8.56indirect
crates.iozmij1.0.23indirect
Dependency advisories 0

Installing crates:constant_time_eq@0.6.0 pulls in 54 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.