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

neilharvey / FileSignatures

A small library for detecting the type of a file based on header signature (also known as magic number).

C# · Rich Text FormatMIT★ 322 stars⑂ 46 forkssince Dec 2016View on GitHub ↗

neilharvey/FileSignatures holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (75/100) and lowest on Engineering Quality (38/100). It was last updated today. 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

Neil HarveyPersonal account
15 followers19 public repossince Sep 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
NuGetFileSignatures7.3.0-290 days agofileformatmimetypemediaheadersignaturedetection

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
8.3/36Commit cadence12/52 weeks with commits
13.6/18Commit volume32 commits in the last year
6/10OpenSSF Scorecard: Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year32
human_commit_share0.94
days_since_last_push0
active_weeks_last_year12
How it's scored
27/27Ships releases28 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~50.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count28
latest_release_tagv7.3
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases50.1
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?

64Moderate · 17% of overall
How it's scored
40.7/60Stars322 stars
13.8/25Forks46 forks
6.5/15Watchers16 watchers
Inputs used
forks46
stars322
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io
has_pull_request_templateno
How it's scored
70.1/80Total downloads5,592,933 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesFileSignatures
dependents
ecosystemsnuget
total_downloads5,592,933
monthly_downloads
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.4/22.5Commit distributiontop contributor authored 80% of commits
13.5/13.5Contributor breadth15 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.804
How it's scored
30.7/42Issue resolution73% of issues closed
26.5/30PR acceptance45/51 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 3/15 approved changesets -- score normalized to 2
Inputs used
merged_prs45
open_issues15
closed_issues41
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.732
closed_unmerged_prs6
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8.7/25Owner reach15 followers of neilharvey
21.5/25Track record19 public repos, account ~13 yr old
Inputs used
followers15
owner_typeUser
is_verified
owner_loginneilharvey
public_repos19
account_age_days5,079
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 nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history29 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesFileSignatures
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsfile-signature, magic-bytes
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
4.5/7.5Binary-Artifactsbinaries present in source code
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 3/15 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
4.5/7.5Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages8
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 8 resolved dependencies against OSV. 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.

59Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
17/40Legible commit history30 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.319
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapexamples/ConsoleApplication/InspectFormat.csproj, examples/WebApplication/WebApplication.csproj, src/FileSignatures/FileSignatures.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsexamples/ConsoleApplication/InspectFormat.csproj, examples/WebApplication/WebApplication.csproj, src/FileSignatures/FileSignatures.csproj, test/FileSignatures.Tests/FileSignatures.Tests.csproj
dependency_bot_commit_share0.02
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/93 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes7,003
source_files_sampled93
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples, samples
Inputs used
example_dirsexamples, samples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

322GitHub stars
15contributors
32commits, last 12 months
0days since last push
28releases
1bus factor
15open issues
package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 46 ⇿
0Stars
46Forks
25Releases

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.

010203040504522018-062022-072026-08
Major 0Minor 1Patch 8

Each point covers 8 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-08-14 18:56 UTC

6Binary-Artifactsbinaries present in source code
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 3/15 approved changesets -- score normalized to 2
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
NuGetSystem.Reflection.TypeExtensions4.3.0src/FileSignatures/FileSignatures.csproj
NuGetOpenMcdf3.1.4src/FileSignatures/FileSignatures.csproj
All dependencies 8

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

RegistryPackageVersionRelation
NuGetOpenMcdf3.1.4direct
NuGetSystem.Reflection.TypeExtensions4.3.0direct
NuGetBenchmarkDotNet0.13.12indirect
NuGetFileSignatures4.0.0indirect
NuGetFileSignatures5.2.0-rc1indirect
NuGetMicrosoft.NET.Test.Sdk17.10.0indirect
NuGetxunit2.8.1indirect
NuGetxunit.runner.visualstudio2.8.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 8 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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

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