# GetDKAN/file-fetcher — health index 36/100 (Weak)

> Inspection of the public repository GetDKAN/file-fetcher by inspect.software. It holds a health index of 36 out of 100, placing it in the Weak band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/GetDKAN/file-fetcher
- Report page: https://inspect.software/software/GetDKAN/file-fetcher
- Full JSON report: https://inspect.software/api/repositories/GetDKAN/file-fetcher/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/g/GetDKAN/file-fetcher.svg
- Inspected: 2026-09-17
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 45/100 | Weak |
| Community & Adoption | 17% | 35/100 | Weak |
| Sustainability & Governance | 23% | 59/100 | Moderate |
| Engineering Quality | 19% | 55/100 | Moderate |
| Security | 16% | 1/100 | Critical |
| AI Readiness | 4% | 41/100 | Weak |

The weighted overall 41 is calibrated to 36 on the published index scale (record calibration 2026-08-02).

## Repository facts

| Field | Value |
|---|---|
| Description | Utility library to fetch remote files. |
| Classification | library |
| Primary language | PHP |
| License | GPL-3.0 |
| Stars | 4 |
| Forks | 0 |
| Created | 2019-07-09 |
| Last push | 2026-08-06 |
| Latest release | 5.1.2 |
| Commits (last year) | 3 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| packagist | getdkan/file-fetcher | 5.1.2 | 3,596 |

## Vitality — 45/100 (Weak)

Is the project alive — is code being written and are releases shipping? Weight: 21% of the overall index.

### Development activity — 28/100 (At Risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | partial | 18 / 36 | last push 41 days ago |
| Commit cadence | partial | 1.4 / 36 | 2/52 weeks with commits |
| Commit volume | partial | 5.4 / 18 | 3 commits in the last year |
| OpenSSF Scorecard: Maintained | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Release discipline — 70/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 30 releases published |
| Release recency | partial | 16.2 / 36 | latest release 210 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~93.6 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Abandonment — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | no human commit for 210 days, with nothing left unanswered; held at dormant by a release within the year |

## Community & Adoption — 35/100 (Weak)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 17% of the overall index.

### Popularity & adoption — 13/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 7.7 / 60 | 4 stars |
| Forks | not met | 0 / 25 | 0 forks |
| Watchers | partial | 5.6 / 15 | 11 watchers |

### Community health — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (GPL-3.0) |
| CONTRIBUTING guide | not met | 0 / 18 | — |
| Code of conduct | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

### Ecosystem adoption (downloads) — 51/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 47.4 / 80 | 3,596 downloads/month across packagist |
| Registry dependents | partial | 4 / 20 | 3 packages depend on it |

## Sustainability & Governance — 59/100 (Moderate)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 23% of the overall index.

### Maintainer resilience (bus factor) — 34/100 (At Risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 10.5 / 22.5 | top contributor authored 53% of commits |
| Contributor breadth | partial | 10.8 / 13.5 | 8 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 54/100 (Moderate)

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 10.5 / 42 | 25% of issues closed |
| PR acceptance | partial | 28.5 / 30 | 37/39 decided PRs merged |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

### Ownership & stewardship — 67/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 12.4 / 25 | 52 followers of GetDKAN |
| Track record | met | 25 / 25 | 103 public repos, account ~9 yr old |

### Package maintenance — 91/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on packagist |
| Publish recency | partial | 26 / 35 | latest publish 210 days ago |
| Version history | met | 20 / 20 | 30 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 55/100 (Moderate)

Are baseline engineering and documentation practices in place? Weight: 19% of the overall index.

### Engineering practices — 58/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | phpcs.xml |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | met | 10 / 10 | — |

## Security — 1/100 (Critical)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 1/100 (Critical)

Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Security policy (SECURITY.md) | not met | 0 / 30 | — |
| Dependabot config | not met | 0 / 25 | — |
| Dependency lockfiles | excluded | 0 / 25 | published library — lockfiles are an application concern, not expected |
| CodeQL workflow | not met | 0 / 20 | — |

### High-Risk Jurisdiction Exposure — 100/100 (Exceptional)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 41/100 (Weak)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 39/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | partial | 38.9 / 40 | 35 of 48 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 37/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | phpcs.xml |
| Static type checking | not met | 0 / 11 | — |
| Reproducible environment | not met | 0 / 10 | — |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 48 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Code legibility for models — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | not met | 0 / 45 | PHP without a type-check config |
| Manageable file sizes | met | 55 / 55 | 0/15 source files over 60KB |

## 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

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt