Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-06 12:52 UTC

pipedrive / client-php

Pipedrive API client for PHP

PHPMIT★ 62 stars⑂ 64 forkssince Feb 2020View on GitHub ↗

pipedrive/client-php holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (81/100) and lowest on AI Readiness (36/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

Pipedrive IncOrganization
120 followers35 public repossince Jan 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmpipedrivepoints to another repo — not scored33.5.0307,34229414 days ago
Packagistpipedrive/pipedrive17.3.045,77710162 days agosalescrmcontactspipelinecustomerspipedrivedealssales-pipeline

Metrics by category

Vitality

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

66Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
15.2/36Commit cadence — 22/52 weeks with commits
18/18Commit volume — 113 commits in the last year
7/10OpenSSF Scorecard: Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year113
human_commit_share0.86
days_since_last_push0
active_weeks_last_year22
How it's scored
27/27Ships releases — 11 releases published
0/36Release recency — latest release 811 days ago
19.8/27Release cadence — a release every ~113.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tag6.7.0
releases_from_tagsno
days_since_latest_release811
mean_days_between_releases113.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?

55Moderate · 17% of overall
How it's scored
29/60Stars — 62 stars
15/25Forks — 64 forks
5.6/15Watchers — 11 watchers
Inputs used
forks64
stars62
watchers11
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
62.1/80Monthly downloads — 45,777 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packagespipedrive/pipedrive
dependents0
ecosystemspackagist
total_downloads1,429,292
monthly_downloads45,777

Sustainability & Governance

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

81Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
17.3/22.5Commit distribution — top contributor authored 23% of commits
13.5/13.5Contributor breadth — 20 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor3
contributors_sampled20
top_contributor_share0.23
How it's scored
41.1/42Issue resolution — 98% of issues closed
19.4/30PR acceptance — 125/193 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs125
open_issues2
closed_issues87
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.978
closed_unmerged_prs68
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
0/20Verified domain
15/25Owner reach — 120 followers of pipedrive
23.3/25Track record — 35 public repos, account ~16 yr old
Inputs used
followers120
owner_typeOrganization
is_verified
owner_loginpipedrive
public_repos35
account_age_days6,033

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 2 out of 16 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
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.2/2.5CI-Tests — 2 out of 16 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
7.5/7.5Code-Review — all changesets reviewed
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
5.2/7.5Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages37
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:pipedrive@33.5.0 runtime dependency closure — what installing the published package pulls in — 37 packages. 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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18/40Legible commit history — 29 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.337
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
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
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.05
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
53/55Manageable file sizes — 43/1,210 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes283,030
source_files_sampled1,210
oversized_source_files43

Key facts

62GitHub stars
20contributors
113commits, last 12 months
0days since last push
11releases
3bus factor
2open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'pipedrive' points at a different repository (https://github.com/pipedrive/client-nodejs); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 64 ⇿
0Stars
64Forks
11Releases

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.

01325385063756332020-042023-032026-02
Major 4Minor 3Patch 4

Each point covers 6 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-08-06 12:52 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
1CI-Tests2 out of 16 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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 2
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/guzzle^7.3composer.json
Packagistguzzlehttp/psr7^2.0composer.json
All dependencies 8

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzledirect
Packagistguzzlehttp/psr7direct
Packagistext-curlindirect
Packagistext-jsonindirect
Packagistext-mbstringindirect
Packagistpestphp/pestindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Dependency advisories 0

Installing npm:pipedrive@33.5.0 pulls in 37 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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

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

How one result sits in the wider record: aggregate statisticsnpm, Packagist.