Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 03:50 UTC

GetDKAN / file-fetcher

Utility library to fetch remote files.

PHPGPL-3.0★ 4 stars⑂ 0 forkssince Jul 2019View on GitHub ↗
KindLibraryhow this is determined

GetDKAN/file-fetcher holds a health index of 36 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (59/100) and lowest on Security (1/100). It was last updated 41 days ago. A single contributor accounts for most of its recent work.

36
overall / 100
Weak

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.

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

Ownership

DKANOrganization
52 followers103 public repossince Jan 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistgetdkan/file-fetcher5.1.23,59630210 days ago

Metrics by category

Vitality

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

45Weak · 21% of overall

Development activity

28At Risk
How it's scored
18/36Push recency — last push 41 days ago
1.4/36Commit cadence — 2/52 weeks with commits
5.4/18Commit volume — 3 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push41
active_weeks_last_year2

Release discipline

70Good
How it's scored
27/27Ships releases — 30 releases published
16.2/36Release recency — latest release 210 days ago
19.8/27Release cadence — a release every ~93.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count30
latest_release_tag5.1.2
releases_from_tagsno
days_since_latest_release210
mean_days_between_releases93.6

Community & Adoption

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

35Weak · 17% of overall

Popularity & adoption

13Critical
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 0 forks
5.6/15Watchers — 11 watchers
Inputs used
forks0
stars4
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
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_servicescircleci.com
has_pull_request_templateno

Ecosystem adoption (downloads)

51Moderate
How it's scored
47.4/80Monthly downloads — 3,596 downloads/month across packagist
4/20Registry dependents — 3 packages depend on it
Inputs used
packagesgetdkan/file-fetcher
dependents3
ecosystemspackagist
total_downloads205,550
monthly_downloads3,596
unverified_packages_excluded—

Sustainability & Governance

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

59Moderate · 23% of overall

Maintainer resilience (bus factor)

34At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.5/22.5Commit distribution — top contributor authored 53% of commits
10.8/13.5Contributor breadth — 8 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.532

Issue & PR responsiveness

54Moderate
How it's scored
10.5/42Issue resolution — 25% of issues closed
28.5/30PR acceptance — 37/39 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_prs37
open_issues3
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.25
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.

Ownership & stewardship

67Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.4/25Owner reach — 52 followers of GetDKAN
25/25Track record — 103 public repos, account ~9 yr old
Inputs used
followers52
owner_typeOrganization
is_verifiedno
owner_loginGetDKAN
public_repos103
account_age_days3,519

Package maintenance

91Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
26/35Publish recency — latest publish 210 days ago
20/20Version history — 30 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgetdkan/file-fetcher
ecosystemspackagist
any_deprecatedno
min_days_since_publish210

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall

Engineering practices

58Moderate
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — phpcs.xml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
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?

1Critical · 16% of overall

Security posture

1Critical
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
lockfiles—
manifestscomposer.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

41Weak · 4% of overall

Agent context & guidance

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

Verify loop (build / test / typecheck)

37Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpcs.xml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 48
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/15 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes9,011
source_files_sampled15
oversized_source_files0

Key facts

4GitHub stars
8contributors
3commits, last 12 months
41days since last push
30releases
1bus factor
3open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/GetDKAN/file-fetcher: run: repo unreachable: Get "https://api.github.com/repos/GetDKAN/file-fetcher": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: net/http: TLS handshake timeout); skipping Scorecard checks

More detail

Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistgetdkan/procrastinator^5.0.3composer.json
Packagistguzzlehttp/guzzle^7.4.5composer.json
All dependencies 11

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

RegistryPackageVersionRelation
Packagistgetdkan/procrastinator—direct
Packagistguzzlehttp/guzzle—direct
Packagistext-curl—indirect
Packagistgetdkan/contracts—indirect
Packagistgetdkan/mock-chain—indirect
Packagistmikey179/vfsstream—indirect
Packagistphp—indirect
Packagistphpunit/phpunit—indirect
Packagistrector/rector—indirect
Packagistsquizlabs/php_codesniffer—indirect
Packagistsymfony/phpunit-bridge—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 GetDKAN/file-fetcher. Read them side by side →

99nextcloud/server☁️ Nextcloud server, a safe home for all your dataExceptional99swagger-api/swagger-uiSwagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.Exceptional99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional99stripe/stripe-phpPHP library for the Stripe API. Exceptional99grpc/grpcC++ based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)Exceptional99WordPress/gutenbergThe Block Editor project for WordPress and beyond. Plugin is available from the official repository.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 — Packagist.