Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 15:29 UTC

eiriksm / cosy-composer

PHPAGPL-3.0★ 1 star⑂ 4 forkssince Mar 2017View on GitHub ↗

eiriksm/cosy-composer holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on Community & Adoption (37/100). It was last updated 13 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Eirik Stanghelle MorlandPersonal account
112 followers436 public repossince Jun 2011@packagist

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 publish
Packagisteiriksm/cosy-composer1.4.91,78811313 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 13 days ago
13.8/36Commit cadence — 20/52 weeks with commits
17.2/18Commit volume — 81 commits in the last year
10/10OpenSSF Scorecard: Maintained — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year81
human_commit_share0.97
days_since_last_push13
active_weeks_last_year20

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 13 days ago
27/27Release cadence — a release every ~3.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag1.4.9
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases3.6
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?

37Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
4/25Forks — 4 forks
0/15Watchers — 1 watchers
Inputs used
forks4
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (AGPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateno
How it's scored
43.4/80Monthly downloads — 1,788 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packageseiriksm/cosy-composer
dependents0
ecosystemspackagist
total_downloads194,482
monthly_downloads1,788
unverified_packages_excluded—

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 factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.999
How it's scored
39.4/42Issue resolution — 94% of issues closed
26.9/30PR acceptance — 415/462 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs415
open_issues3
closed_issues46
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.939
closed_unmerged_prs47
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.8/25Owner reach — 112 followers of eiriksm
25/25Track record — 436 public repos, account ~15 yr old
Inputs used
followers112
owner_typeUser
is_verified—
owner_logineiriksm
public_repos436
account_age_days5,563
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 packagist
35/35Publish recency — latest publish 13 days ago
20/20Version history — 113 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageseiriksm/cosy-composer
ecosystemspackagist
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicscomposer, composer-package, php
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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/7.5Code-Review — Found 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 10 contributing companies or organizations
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
7.5/7.5Maintained — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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_aggregate6
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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 82 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.845
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
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.03
How it's scored
0/45Type-checkable code — PHP without a type-check config
54.8/55Manageable file sizes — 1/223 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes64,261
source_files_sampled223
oversized_source_files1

Key facts

1GitHub stars
2contributors
81commits, last 12 months
13days since last push
100releases
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

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks

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.

1223344412017-042020-122024-09

Each point covers 7 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-14 15:29 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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 24
RegistryPackageVersion constraintManifest
Packagistbitbucket/client^3||^4composer.json
Packagistguzzlehttp/guzzle^7.4composer.json
Packagisthttp-interop/http-factory-guzzle^1.1composer.json
Packagistknplabs/github-api^3.0composer.json
Packagistleague/flysystem^2.0 || ^3.0composer.json
Packagistm4tthumphrey/php-gitlab-api^10 || ^11composer.json
Packagistpeterpostmann/parse_uri^1.0composer.json
Packagistsymfony/polyfill-php80^1.0composer.json
Packagistsymfony/process^5.4 || ^6 || ^7composer.json
Packagistsymfony/yaml^5.4 || ^6 || ^7composer.json
Packagistviolinist-dev/allow-list-handler^1.0composer.json
Packagistviolinist-dev/commit-message-creator^2.1composer.json
Packagistviolinist-dev/composer-changelog-fetcher^5.2.0composer.json
Packagistviolinist-dev/composer-updater^2.0composer.json
Packagistviolinist-dev/git-log-format^1.2.0composer.json
Packagistviolinist-dev/process-factory^3.0composer.json
Packagistviolinist-dev/project-data^1.1.1composer.json
Packagistviolinist-dev/repo-and-token-to-clone-url^1.0composer.json
Packagistviolinist-dev/slug-from-url^1composer.json
Packagistviolinist-dev/symfony-cloud-security-checker^3composer.json
Packagistviolinist-dev/timeframe-handler^1.0composer.json
Packagistviolinist-dev/violinist-config^2.10composer.json
Packagistviolinist-dev/violinist-messages^2.1.0composer.json
Packagistwa72/simplelogger^1.0composer.json
All dependencies 32

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

RegistryPackageVersionRelation
Packagistbitbucket/client—direct
Packagistguzzlehttp/guzzle—direct
Packagisthttp-interop/http-factory-guzzle—direct
Packagistknplabs/github-api—direct
Packagistleague/flysystem—direct
Packagistm4tthumphrey/php-gitlab-api—direct
Packagistpeterpostmann/parse_uri—direct
Packagistsymfony/polyfill-php80—direct
Packagistsymfony/process—direct
Packagistsymfony/yaml—direct
Packagistviolinist-dev/allow-list-handler—direct
Packagistviolinist-dev/commit-message-creator—direct
Packagistviolinist-dev/composer-changelog-fetcher—direct
Packagistviolinist-dev/composer-updater—direct
Packagistviolinist-dev/git-log-format—direct
Packagistviolinist-dev/process-factory—direct
Packagistviolinist-dev/project-data—direct
Packagistviolinist-dev/repo-and-token-to-clone-url—direct
Packagistviolinist-dev/slug-from-url—direct
Packagistviolinist-dev/symfony-cloud-security-checker—direct
Packagistviolinist-dev/timeframe-handler—direct
Packagistviolinist-dev/violinist-config—direct
Packagistviolinist-dev/violinist-messages—direct
Packagistwa72/simplelogger—direct
Packagistcomposer/semver—indirect
Packagistext-json—indirect
Packagistphp-coveralls/php-coveralls—indirect
Packagistphp-http/guzzle7-adapter—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpunit/phpunit—indirect
Packagistslevomat/coding-standard—indirect
Packagistsquizlabs/php_codesniffer—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.

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.