Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 06:22 UTC

vaimo / composer-changelogs

Provide information about package changes based on change-log files that are bundled with releases; provide tools for generating documentation files from change-log JSON sources

PHPMIT★ 11 stars⑂ 2 forkssince Aug 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

vaimo/composer-changelogs holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (66/100) and lowest on AI Readiness (32/100). It was last updated today. 2 contributors account for most of its recent work.

57
overall / 100
Moderate

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.

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

Ownership

VaimoOrganization
41 followers117 public repossince Mar 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistvaimo/composer-changelogs2.0.02,64245141 days agochangelog-filesgrouped-changessemantic-meaning-for-changechangelog-jsondocumentation-generators

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.8/36Commit cadence4/52 weeks with commits
11.1/18Commit volume16 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year16
human_commit_share1
days_since_last_push0
active_weeks_last_year4
How it's scored
27/27Ships releases7 releases published
27/36Release recencylatest release 141 days ago
5.4/27Release cadencea release every ~440.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count7
latest_release_tag2.0.0
releases_from_tagsno
days_since_latest_release141
mean_days_between_releases440.9
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?

38Weak · 17% of overall
How it's scored
16.2/60Stars11 stars
0/25Forks2 forks
3.9/15Watchers6 watchers
Inputs used
forks2
stars11
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
45.6/80Monthly downloads2,642 downloads/month across packagist
6.9/20Registry dependents10 packages depend on it
Inputs used
packagesvaimo/composer-changelogs
dependents10
ecosystemspackagist
total_downloads161,684
monthly_downloads2,642
unverified_packages_excluded

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.9/22.5Commit distributiontop contributor authored 47% of commits
8.1/13.5Contributor breadth6 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled6
top_contributor_share0.472
How it's scored
18/42Issue resolution43% of issues closed
21.8/30PR acceptance8/11 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/12 approved changesets -- score normalized to 1
Inputs used
merged_prs8
open_issues4
closed_issues3
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.429
closed_unmerged_prs3
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.7/25Owner reach41 followers of vaimo
25/25Track record117 public repos, account ~14 yr old
Inputs used
followers41
owner_typeOrganization
is_verified
owner_loginvaimo
public_repos117
account_age_days5,251
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 packagist
35/35Publish recencylatest publish 141 days ago
20/20Version history45 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesvaimo/composer-changelogs
ecosystemspackagist
any_deprecatedno
min_days_since_publish141

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpcs.xml
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicschangelog, composer-plugin, generator, composer-commands
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?

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.8/2.5CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 2/12 approved changesets -- score normalized to 1
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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
advisories3
affected_packages1
assessed_packages41
unassessed_packages4
affected_by_severityhigh 1
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 41 resolved dependencies against OSV. 4 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.9/40Legible commit history13 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.13
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpcs.xml
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/74 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes7,507
source_files_sampled74
oversized_source_files0

Key facts

11GitHub stars
6contributors
16commits, last 12 months
0days since last push
7releases
2bus factor
4open issues
Packagistpackage ecosystems

More detail

Star and fork history 11 ★ / 2 ⇿
11Stars
2Forks
5Releases

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.

02468101211212018-102021-122025-01
Major 1Minor 1Patch 3

Each point covers 6 days.

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-07-22 06:22 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests3 out of 8 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/12 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagistmustache/mustache>=v2.12.0composer.json
Packagistseld/jsonlint^1.7.1composer.json
Packagistcamspiers/json-pretty^1.0.2composer.json
Packagistsymfony/console^4.0 || ^5.0 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/process>=4.2composer.json
All dependencies 45

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

RegistryPackageVersionRelation
Packagistcamspiers/json-pretty1.0.2direct
Packagistmustache/mustache3.2.0direct
Packagistseld/jsonlint1.11.0direct
Packagistsymfony/console8.0.11direct
Packagistsymfony/process8.0.11direct
Packagistcomposer-plugin-apiindirect
Packagistcomposer/ca-bundle1.5.11indirect
Packagistcomposer/class-map-generator1.7.3indirect
Packagistcomposer/composer2.9.8indirect
Packagistcomposer/metadata-minifier1.0.0indirect
Packagistcomposer/pcre3.3.2indirect
Packagistcomposer/semver3.4.4indirect
Packagistcomposer/spdx-licenses1.6.0indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistjustinrainbow/json-schema6.8.2indirect
Packagistmarc-mabe/php-enum4.7.2indirect
Packagistpdepend/pdepend2.16.2indirect
Packagistphpcompatibility/php-compatibilityindirect
Packagistphpcompatibility/php-compatibility9.3.5indirect
Packagistphpmd/phpmd2.15.0indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/log3.0.2indirect
Packagistreact/promise3.3.0indirect
Packagistseld/phar-utils1.2.1indirect
Packagistseld/signal-handler2.0.2indirect
Packagistsquizlabs/php_codesnifferindirect
Packagistsquizlabs/php_codesniffer3.13.5indirect
Packagistsymfony/config7.4.10indirect
Packagistsymfony/dependency-injection7.4.10indirect
Packagistsymfony/deprecation-contracts3.7.0indirect
Packagistsymfony/filesystem7.4.11indirect
Packagistsymfony/finder8.0.8indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.37.0indirect
Packagistsymfony/polyfill-intl-normalizer1.37.0indirect
Packagistsymfony/polyfill-mbstring1.37.0indirect
Packagistsymfony/polyfill-php731.37.0indirect
Packagistsymfony/polyfill-php801.37.0indirect
Packagistsymfony/polyfill-php811.37.0indirect
Packagistsymfony/polyfill-php841.37.0indirect
Packagistsymfony/service-contracts3.7.0indirect
Packagistsymfony/string8.0.11indirect
Packagistsymfony/var-exporter8.0.9indirect
Packagistvaimo/composer-changelogs-localindirect
Packagistvaimo/composer-changelogs-proxy1.0.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 41 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 4 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
composer/composer2.9.8indirecthigh32.10.2

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

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