Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 21:50 UTC

apimatic / core-lib-php

Core logic and the utilities for the APIMatic's PHP SDKs

PHPMIT★ 7 stars⑂ 4 forkssince Jul 2022View on GitHub ↗

apimatic/core-lib-php holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (74/100) and lowest on AI Readiness (39/100). It was last updated 60 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

APIMaticOrganization · verified domain
21 followers143 public repossince Aug 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistapimatic/core0.3.18430,4753260 days agophpcorecorelibapimatic

Metrics by category

Vitality

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

54Moderate · 21% of overall
How it's scored
18/36Push recency — last push 60 days ago
2.8/36Commit cadence — 4/52 weeks with commits
7/18Commit volume — 5 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year5
human_commit_share0.99
days_since_last_push60
active_weeks_last_year4
How it's scored
27/27Ships releases — 32 releases published
36/36Release recency — latest release 60 days ago
19.8/27Release cadence — a release every ~92.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count32
latest_release_tag0.3.18
releases_from_tagsno
days_since_latest_release60
mean_days_between_releases92.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?

56Moderate · 17% of overall
How it's scored
12.6/60Stars — 7 stars
4/25Forks — 4 forks
1.7/15Watchers — 3 watchers
Inputs used
forks4
stars7
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
75.1/80Monthly downloads — 430,475 downloads/month across packagist
14.1/20Registry dependents — 129 packages depend on it
Inputs used
packagesapimatic/core
dependents129
ecosystemspackagist
total_downloads4,478,932
monthly_downloads430,475
unverified_packages_excluded—

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.1/22.5Commit distribution — top contributor authored 82% of commits
13.5/13.5Contributor breadth — 11 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.819
How it's scored
39.5/42Issue resolution — 94% of issues closed
30/30PR acceptance — 46/46 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 26/29 approved changesets -- score normalized to 8
Inputs used
merged_prs46
open_issues2
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.941
closed_unmerged_prs0
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
9.7/25Owner reach — 21 followers of apimatic
25/25Track record — 143 public repos, account ~12 yr old
Inputs used
followers21
owner_typeOrganization
is_verifiedyes
owner_loginapimatic
public_repos143
account_age_days4,441

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 60 days ago
20/20Version history — 32 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesapimatic/core
ecosystemspackagist
any_deprecatedno
min_days_since_publish60

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 5 out of 29 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicsphp
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?

64Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.2/2.5CI-Tests — 5 out of 29 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
6/7.5Code-Review — Found 26/29 approved changesets -- score normalized to 8
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 1 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.5/5SAST — SAST tool is not run on all commits -- score normalized to 1
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_aggregate5.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
advisories0
affected_packages0
assessed_packages59
unassessed_packages0
affected_by_severitynone
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 59 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.

39Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
23.7/40Legible commit history — 44 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.444
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
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_configno
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
54.5/55Manageable file sizes — 1/101 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes74,601
source_files_sampled101
oversized_source_files1

Key facts

7GitHub stars
11contributors
5commits, last 12 months
60days since last push
32releases
1bus factor
2open 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 ★ / 4 ⇿
0Stars
4Forks
18Releases

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.

1223344412023-032024-012024-12
Major 0Minor 1Patch 17

Each point covers 2 days.

OpenSSF Scorecard 5.5 / 10
5.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-10-19 21:50 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
1CI-Tests5 out of 29 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 26/29 approved changesets -- score normalized to 8
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 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
1SASTSAST tool is not run on all commits -- score normalized to 1
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Packagistpsr/log^1.1.4 || ^2.0.0 || ^3.0.0composer.json
Packagistapimatic/core-interfaces~0.1.5composer.json
Packagistapimatic/jsonmapper^3.1.1composer.json
Packagistsymfony/http-foundation^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
All dependencies 59

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

RegistryPackageVersionRelation
Packagistapimatic/core-interfaces0.1.5direct
Packagistapimatic/jsonmapper3.1.7direct
Packagistpsr/log3.0.2direct
Packagistsymfony/http-foundation7.4.16direct
Packagistcomposer/pcre3.3.2indirect
Packagistcomposer/semver3.4.4indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistdoctrine/deprecations1.1.6indirect
Packagistdoctrine/instantiator2.0.0indirect
Packagistfelixfbecker/advanced-json-rpc3.2.1indirect
Packagistmicrosoft/tolerant-php-parser0.1.2indirect
Packagistmyclabs/deep-copy1.14.0indirect
Packagistnetresearch/jsonmapper4.5.0indirect
Packagistnikic/php-parser5.8.0indirect
Packagistphan/phan5.4.5indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphp-jsonpointer/php-jsonpointer3.0.2indirect
Packagistphpdocumentor/reflection-common2.2.0indirect
Packagistphpdocumentor/reflection-docblock5.6.7indirect
Packagistphpdocumentor/type-resolver1.12.0indirect
Packagistphpstan/phpdoc-parser2.3.3indirect
Packagistphpunit/php-code-coverage9.2.32indirect
Packagistphpunit/php-file-iterator3.0.6indirect
Packagistphpunit/php-invoker3.1.1indirect
Packagistphpunit/php-text-template2.0.4indirect
Packagistphpunit/php-timer5.0.3indirect
Packagistphpunit/phpunit9.6.36indirect
Packagistpsr/container2.0.2indirect
Packagistsabre/event5.1.7indirect
Packagistsebastian/cli-parser1.0.2indirect
Packagistsebastian/code-unit1.0.8indirect
Packagistsebastian/code-unit-reverse-lookup2.0.3indirect
Packagistsebastian/comparator4.0.10indirect
Packagistsebastian/complexity2.0.3indirect
Packagistsebastian/diff4.0.6indirect
Packagistsebastian/environment5.1.5indirect
Packagistsebastian/exporter4.0.9indirect
Packagistsebastian/global-state5.0.8indirect
Packagistsebastian/lines-of-code1.0.4indirect
Packagistsebastian/object-enumerator4.0.4indirect
Packagistsebastian/object-reflector2.0.4indirect
Packagistsebastian/recursion-context4.0.7indirect
Packagistsebastian/resource-operations3.0.4indirect
Packagistsebastian/type3.2.1indirect
Packagistsebastian/version3.0.2indirect
Packagistsquizlabs/php_codesniffer3.13.6indirect
Packagistsymfony/console7.4.3indirect
Packagistsymfony/deprecation-contracts3.7.1indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.33.0indirect
Packagistsymfony/polyfill-intl-normalizer1.33.0indirect
Packagistsymfony/polyfill-mbstring1.38.2indirect
Packagistsymfony/polyfill-php801.37.0indirect
Packagistsymfony/service-contracts3.6.1indirect
Packagistsymfony/string7.4.0indirect
Packagisttheseer/tokenizer1.3.1indirect
Packagisttysonandre/var_representation_polyfill0.1.3indirect
Packagistwebmozart/assert2.4.1indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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

How one result sits in the wider record: aggregate statistics — Packagist.