Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 17:46 UTC

mindeng / nom-exif

Exif/metadata parsing library written in pure Rust, both image (JPEG, PNG, WebP, HEIC/HEIF, AVIF, TIFF, Phase One IIQ, Fujifilm RAF, Canon CR3) and video/audio (MP4, MOV, 3GP, MKV, WEBM, MKA) files are supported.

RustMIT★ 123 stars⑂ 19 forkssince Feb 2024View on GitHub ↗
KindLibraryhow this is determined
#exif#heif#jpeg#metadata#mp4#nom#parser#quicktime#rust#matroska#mkv#webm#mov#raw#tiff#cr3

mindeng/nom-exif holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Security (47/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Min DengPersonal account
39 followers70 public repossince Jul 2011

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.ionom-exif3.8.019,912605 days agoexifmetadataparsingparser-implementations

Metrics by category

Vitality

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

84Excellent · 21% of overall

Development activity

74Good
How it's scored
36/36Push recency — last push 5 days ago
9.7/36Commit cadence — 14/52 weeks with commits
18/18Commit volume — 295 commits in the last year
10/10OpenSSF Scorecard: Maintained — 25 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year295
human_commit_share1
days_since_last_push5
active_weeks_last_year14

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 53 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~11.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count53
latest_release_tagv3.8.0
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases11.9
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?

54Moderate · 17% of overall

Popularity & adoption

46Weak
How it's scored
33.8/60Stars — 123 stars
10.5/25Forks — 19 forks
1.7/15Watchers — 3 watchers
Inputs used
forks19
stars123
watchers3
growth_stateorganic
growth_factor_pct100

Community health

50Moderate
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_servicescodecov.io, github.com, shields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

72Good
How it's scored
57.3/80Monthly downloads — 19,912 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnom-exif
dependents—
ecosystemscrates
total_downloads192,420
monthly_downloads19,912
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

Maintainer resilience (bus factor)

24At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.3/22.5Commit distribution — top contributor authored 94% of commits
13.5/13.5Contributor breadth — 12 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.943

Issue & PR responsiveness

82Excellent
How it's scored
40/42Issue resolution — 95% of issues closed
27.4/30PR acceptance — 21/23 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/17 approved changesets -- score normalized to 1
Inputs used
merged_prs21
open_issues2
closed_issues41
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.953
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1

Ownership & stewardship

58Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.5/25Owner reach — 39 followers of mindeng
25/25Track record — 70 public repos, account ~15 yr old
Inputs used
followers39
owner_typeUser
is_verified—
owner_loginmindeng
public_repos70
account_age_days5,535
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 5 days ago
20/20Version history — 60 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnom-exif
ecosystemscrates
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall

Engineering practices

68Good
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://crates.io/crates/nom-exif
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicsexif, heif, jpeg, metadata, mp4, nom, parser, quicktime, rust, matroska, mkv, webm, mov, raw, tiff, cr3
has_wikiyes
homepagehttps://crates.io/crates/nom-exif
docs_sitehttps://crates.io/crates/nom-exif
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

47Weak · 16% of overall

Security posture

47Weak
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.5/2.5CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/17 approved changesets -- score normalized to 1
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
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 25 commit(s) and 5 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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

53Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.97
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

46Weak
How it's scored
12.6/18One-command bootstrap — Cargo.toml, crates/rexiftool/Cargo.toml, fuzz/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
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
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, crates/rexiftool/Cargo.toml, fuzz/Cargo.toml
dependency_bot_commit_share0

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.9/55Manageable file sizes — 1/49 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes94,112
source_files_sampled49
oversized_source_files1

Key facts

123GitHub stars
12contributors
295commits, last 12 months
5days since last push
53releases
1bus factor
2open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-07: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 123 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 117 ★ / 19 ⇿
117Stars
19Forks
48Releases

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.

Star history is shown as collected on 2026-07-07. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02040608010012011719142024-072025-082026-08
Major 2Minor 15Patch 24

Each point covers 2 days.

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-12 17:46 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests5 out of 5 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/17 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained25 commit(s) and 5 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
crates.ionom8.0Cargo.toml
crates.iothiserror2.0.11Cargo.toml
crates.ioserde1.0Cargo.toml
crates.ioregex1.10Cargo.toml
crates.iochrono0.4Cargo.toml
crates.iotracing0.1.40Cargo.toml
crates.iotokio1.40.0Cargo.toml
crates.iobytes1.7.1Cargo.toml
crates.ioiso6709parse0.1.0Cargo.toml
All dependencies 16

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

RegistryPackageVersionRelation
crates.iobytes—direct
crates.iochrono—direct
crates.ioiso6709parse—direct
crates.ionom—direct
crates.ioregex—direct
crates.ioserde—direct
crates.iothiserror—direct
crates.iotokio—direct
crates.iotracing—direct
crates.ioafl—indirect
crates.ioclap—indirect
crates.ionom-exif—indirect
crates.iorand—indirect
crates.ioserde_json—indirect
crates.iotest-case—indirect
crates.iotracing-subscriber—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with mindeng/nom-exif. Read them side by side →

96tree-sitter/tree-sitterAn incremental parsing system for programming toolsExceptional95lovell/sharpHigh performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, AVIF and TIFF images. Uses the libvips library.Exceptional98wasmerio/wasmer🚀 Fast, secure, lightweight containers based on WebAssemblyExceptional98maplibre/martinBlazing fast and lightweight PostGIS, MBtiles and PMtiles tile server, tile generation, and mbtiles tooling.Exceptional98apache/datafusion-sqlparser-rsExtensible SQL Lexer and Parser for RustExceptional96boa-dev/boaBoa is an embeddable Javascript engine written in Rust.Exceptional

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.