Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-28 23:09 UTC

genkgo / camt

PHP Parser for CAMT messages

PHPMIT★ 97 stars⑂ 76 forkssince Mar 2015View on GitHub ↗

genkgo/camt holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (72/100) and lowest on Vitality (37/100). It was last updated 181 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

GenkgoOrganization
6 followers30 public repossince Jun 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistgenkgo/camt2.10.354,97743336 days ago

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
3.6/36Push recency — last push 181 days ago
2.1/36Commit cadence — 3/52 weeks with commits
9.4/18Commit volume — 10 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year10
human_commit_share0.99
days_since_last_push181
active_weeks_last_year3
How it's scored
27/27Ships releases — 30 releases published
16.2/36Release recency — latest release 336 days ago
19.8/27Release cadence — a release every ~69.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count30
latest_release_tag2.10.3
releases_from_tagsno
days_since_latest_release336
mean_days_between_releases69.2
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?

56Moderate · 17% of overall
How it's scored
32.2/60Stars — 97 stars
15.6/25Forks — 76 forks
6.8/15Watchers — 18 watchers
Inputs used
forks76
stars97
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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
63.2/80Monthly downloads — 54,977 downloads/month across packagist
5.2/20Registry dependents — 5 packages depend on it
Inputs used
packagesgenkgo/camt
dependents5
ecosystemspackagist
total_downloads1,374,711
monthly_downloads54,977

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.6/22.5Commit distribution — top contributor authored 40% of commits
13.5/13.5Contributor breadth — 26 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled26
top_contributor_share0.396
How it's scored
38.6/42Issue resolution — 92% of issues closed
23.8/30PR acceptance — 84/106 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 6/11 approved changesets -- score normalized to 5
Inputs used
merged_prs84
open_issues6
closed_issues69
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.92
closed_unmerged_prs22
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 backing — organization-owned
0/20Verified domain
6.1/25Owner reach — 6 followers of genkgo
22.9/25Track record — 30 public repos, account ~13 yr old
Inputs used
followers6
owner_typeOrganization
is_verified
owner_logingenkgo
public_repos30
account_age_days4,803
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
26/35Publish recency — latest publish 336 days ago
20/20Version history — 43 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgenkgo/camt
ecosystemspackagist
any_deprecatedno
min_days_since_publish336

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.dist.php
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 1 out of 9 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

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
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.2/2.5CI-Tests — 1 out of 9 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
3.8/7.5Code-Review — Found 6/11 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 17 contributing companies or organizations
0/10Dangerous-Workflow — no data
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 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): dangerous_workflow, packaging, pinned_dependencies, signed_releases, token_permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages63
unassessed_packages0
affected_by_severityhigh 1, moderate 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 63 resolved dependencies against OSV. 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.3/40Legible commit history — 47 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.475
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.dist.php
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
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.01
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/115 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes18,124
source_files_sampled115
oversized_source_files0

Key facts

97GitHub stars
26contributors
10commits, last 12 months
181days since last push
30releases
2bus factor
6open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 76 ⇿
0Stars
76Forks
30Releases

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.

01325385063757222015-072021-012026-06
Major 2Minor 16Patch 12

Each point covers 10 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-28 23:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
1CI-Tests1 out of 9 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 6/11 approved changesets -- score normalized to 5
10Contributorsproject has 17 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistmoneyphp/money^4.6composer.json
Packagistjschaedl/iban-validation^2.5composer.json
All dependencies 63

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

RegistryPackageVersionRelation
Packagistjschaedl/iban-validation2.5.1direct
Packagistmoneyphp/money4.7.0direct
Packagistclue/ndjson-react1.3.0indirect
Packagistcomposer/pcre3.3.2indirect
Packagistcomposer/semver3.4.3indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistevenement/evenement3.0.2indirect
Packagistfidry/cpu-core-counter1.2.0indirect
Packagistfriendsofphp/php-cs-fixer3.75.0indirect
Packagistmyclabs/deep-copy1.13.1indirect
Packagistnikic/php-parser5.4.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpstan/phpstan2.1.14indirect
Packagistphpunit/php-code-coverage10.1.16indirect
Packagistphpunit/php-file-iterator4.1.0indirect
Packagistphpunit/php-invoker4.0.0indirect
Packagistphpunit/php-text-template3.0.1indirect
Packagistphpunit/php-timer6.0.0indirect
Packagistphpunit/phpunit10.5.46indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/event-dispatcher1.0.0indirect
Packagistpsr/log3.0.2indirect
Packagistreact/cache1.2.0indirect
Packagistreact/child-process0.6.6indirect
Packagistreact/dns1.13.0indirect
Packagistreact/event-loop1.5.0indirect
Packagistreact/promise3.2.0indirect
Packagistreact/socket1.16.0indirect
Packagistreact/stream1.4.0indirect
Packagistsebastian/cli-parser2.0.1indirect
Packagistsebastian/code-unit2.0.0indirect
Packagistsebastian/code-unit-reverse-lookup3.0.0indirect
Packagistsebastian/comparator5.0.3indirect
Packagistsebastian/complexity3.2.0indirect
Packagistsebastian/diff5.1.1indirect
Packagistsebastian/environment6.1.0indirect
Packagistsebastian/exporter5.1.2indirect
Packagistsebastian/global-state6.0.2indirect
Packagistsebastian/lines-of-code2.0.2indirect
Packagistsebastian/object-enumerator5.0.0indirect
Packagistsebastian/object-reflector3.0.0indirect
Packagistsebastian/recursion-context5.0.0indirect
Packagistsebastian/type4.0.0indirect
Packagistsebastian/version4.0.1indirect
Packagistsymfony/console6.4.21indirect
Packagistsymfony/deprecation-contracts3.5.1indirect
Packagistsymfony/event-dispatcher6.4.13indirect
Packagistsymfony/event-dispatcher-contracts3.5.1indirect
Packagistsymfony/filesystem6.4.13indirect
Packagistsymfony/finder6.4.17indirect
Packagistsymfony/options-resolver6.4.16indirect
Packagistsymfony/polyfill-ctype1.32.0indirect
Packagistsymfony/polyfill-intl-grapheme1.32.0indirect
Packagistsymfony/polyfill-intl-normalizer1.32.0indirect
Packagistsymfony/polyfill-mbstring1.32.0indirect
Packagistsymfony/polyfill-php801.32.0indirect
Packagistsymfony/polyfill-php811.32.0indirect
Packagistsymfony/process6.4.20indirect
Packagistsymfony/service-contracts3.5.1indirect
Packagistsymfony/stopwatch6.4.19indirect
Packagistsymfony/string6.4.21indirect
Packagisttheseer/tokenizer1.2.3indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 63 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
phpunit/phpunit10.5.46indirecthigh112.5.8
symfony/process6.4.20indirectmoderate18.0.5

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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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