Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-02 16:40 UTC

diablomedia / zf1-rest

Rest Component from ZF1

PHPBSD-3-Clause★ 0 stars⑂ 2 forkssince Mar 2018archivedView on GitHub ↗

diablomedia/zf1-rest holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (66/100) and lowest on Community & Adoption (32/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

19
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

Diablo MediaOrganization · verified domain
4 followers142 public repossince Dec 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistdiablomedia/zendframework1-rest1.0.96,43910260 days agoframeworkzf1

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
0.7/36Commit cadence — 1/52 weeks with commits
8.1/18Commit volume — 7 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year7
human_commit_share0.36
days_since_last_push0
active_weeks_last_year1
How it's scored
27/27Ships releases — 10 releases published
16.2/36Release recency — latest release 260 days ago
12.6/27Release cadence — a release every ~316.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tag1.0.9
releases_from_tagsno
days_since_latest_release260
mean_days_between_releases316.7
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?

32At Risk · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 2 forks
1.7/15Watchers — 3 watchers
Inputs used
forks2
stars0
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, poser.pugx.org
has_pull_request_templateno
How it's scored
50.8/80Monthly downloads — 6,439 downloads/month across packagist
3.2/20Registry dependents — 2 packages depend on it
Inputs used
packagesdiablomedia/zendframework1-rest
dependents2
ecosystemspackagist
total_downloads336,743
monthly_downloads6,439
unverified_packages_excluded—

Sustainability & Governance

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

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5/22.5Commit distribution — top contributor authored 78% of commits
6.8/13.5Contributor breadth — 5 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.778
How it's scored
42/42Issue resolution — 100% of issues closed
10.7/30PR acceptance — 69/193 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 1/8 approved changesets -- score normalized to 1
Inputs used
merged_prs69
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs124
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
30/30Ownership backing — organization-owned
20/20Verified domain
5/25Owner reach — 4 followers of diablomedia
25/25Track record — 142 public repos, account ~13 yr old
Inputs used
followers4
owner_typeOrganization
is_verifiedyes
owner_logindiablomedia
public_repos142
account_age_days5,047
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
26/35Publish recency — latest publish 260 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdiablomedia/zendframework1-rest
ecosystemspackagist
any_deprecatedno
min_days_since_publish260

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 4 out of 25 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://framework.zend.com/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttp://framework.zend.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.2/2.5CI-Tests — 4 out of 25 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 1/8 approved changesets -- score normalized to 1
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project is archived
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

37Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.2/40Legible commit history — 15 of 36 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.417
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.php, phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 60 of the last 100 commits are automated dependency updates
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_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.6
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_bytes36,626
source_files_sampled15
oversized_source_files0

Key facts

0GitHub stars
5contributors
7commits, last 12 months
0days since last push
10releases
1bus factor
0open issues
Packagistpackage ecosystems

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
6Releases

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.

111222212018-122021-112024-09
Major 0Minor 0Patch 6

Each point covers 6 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-10-02 16:40 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
1CI-Tests4 out of 25 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/8 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
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 8
RegistryPackageVersion constraintManifest
Packagistdiablomedia/zendframework1-exception^1.1.1composer.json
Packagistdiablomedia/zendframework1-config^2.0.5composer.json
Packagistdiablomedia/zendframework1-server^1.0.5composer.json
Packagistdiablomedia/zendframework1-xml^1.0.5composer.json
Packagistdiablomedia/zendframework1-controller^1.0.6composer.json
Packagistdiablomedia/zendframework1-http^1.0.5composer.json
Packagistdiablomedia/zendframework1-service^1.0.4composer.json
Packagistdiablomedia/zendframework1-uri^1.0.5composer.json
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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 — Packagist.