Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 20:20 UTC

zapier / connectors

Connect your agent to the apps you already use - with or without Zapier.

TypeScript · JavaScriptCustom license★ 165 stars⑂ 14 forkssince May 2026View on GitHub ↗
KindLibraryCommand-line toolMCP serverhow this is determined

zapier/connectors holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Security (58/100) and lowest on Vitality (41/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ZapierOrganization · verified domain
1,109 followers298 public repossince Dec 2011

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

Package ecosystems

Metrics by category

Vitality

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

41Weak · 21% of overall
How it's scored
28.8/36Push recencylast push 11 days ago
11.1/36Commit cadence16/52 weeks with commits
18/18Commit volume1,581 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,581
human_commit_share1
days_since_last_push11
active_weeks_last_year16
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

57Moderate · 17% of overall
How it's scored
35.9/60Stars165 stars
9.3/25Forks14 forks
0/15Watchers2 watchers
Inputs used
forks14
stars165
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
49.5/80Monthly downloads5,145 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@zapier/clay-connector, @zapier/alpaca-connector, @zapier/gitlab-connector, @zapier/heygen-connector, @zapier/linear-connector, @zapier/algolia-connector, @zapier/discord-connector, @zapier/dropbox-connector
dependents
ecosystemsnpm
total_downloads
monthly_downloads5,145
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.6/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth18 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.62
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
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): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
21.9/25Owner reach1,109 followers of zapier
25/25Track record298 public repos, account ~14 yr old
Inputs used
followers1,109
owner_typeOrganization
is_verifiedyes
owner_loginzapier
public_repos298
account_age_days5,379

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on npm
35/35Publish recencylatest publish 12 days ago
20/20Version history21 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@zapier/clay-connector, @zapier/alpaca-connector, @zapier/gitlab-connector, @zapier/heygen-connector, @zapier/linear-connector, @zapier/algolia-connector, @zapier/discord-connector, @zapier/dropbox-connector
ecosystemsnpm
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics15 topics
0/10Wiki
Inputs used
topicsagent-skills, agentskills, ai-agents, automation, claude-code, cli, codex, copilot, cursor, integrations, mcp, sdk, skills, typescript, zapier
has_wikino
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?

58Moderate · 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/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTno SAST tool detected
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Pinned-Dependencies, 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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages97
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:@zapier/clay-connector@0.0.6 runtime dependency closure — what installing the published package pulls in — 97 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.

54Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
19.2/40Legible commit history36 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.36
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,959
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingTypeScript (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/1,684 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes17,064
source_files_sampled1,684
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

165GitHub stars
18contributors
1,581commits, last 12 months
11days since last push
0releases
1bus factor
0open issues
package ecosystems

Data collection warnings

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

More detail

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

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.

03581013151462026-072026-082026-09
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-09-05 20:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
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
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 60
RegistryPackageVersion constraintManifest
npm@zapier/connectors-sdk^0.4.6apps/algolia/package.json
npmzod^4.0.0apps/algolia/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/algolia/package.json
npm@zapier/connectors-sdk^0.4.6apps/alpaca/package.json
npmzod^4.0.0apps/alpaca/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/alpaca/package.json
npm@zapier/connectors-sdk^0.4.6apps/clay/package.json
npmzod^4.0.0apps/clay/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/clay/package.json
npm@zapier/connectors-sdk^0.4.6apps/dataforseo/package.json
npmzod^4.0.0apps/dataforseo/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/dataforseo/package.json
npm@zapier/connectors-sdk^0.4.6apps/discord/package.json
npmzod^4.0.0apps/discord/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/discord/package.json
npm@zapier/connectors-sdk^0.4.6apps/dropbox/package.json
npmzod^4.0.0apps/dropbox/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/dropbox/package.json
npm@zapier/connectors-sdk^0.4.6apps/elevenlabs/package.json
npmzod^4.0.0apps/elevenlabs/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/elevenlabs/package.json
npm@zapier/connectors-sdk^0.4.6apps/firecrawl/package.json
npmzod^4.0.0apps/firecrawl/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/firecrawl/package.json
npm@zapier/connectors-sdk^0.4.6apps/gitlab/package.json
npmzod^4.0.0apps/gitlab/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/gitlab/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-ads/package.json
npmzod^4.0.0apps/google-ads/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-ads/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-analytics/package.json
npmzod^4.0.0apps/google-analytics/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-analytics/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-calendar/package.json
npmzod^4.0.0apps/google-calendar/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-calendar/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-contacts/package.json
npmzod^4.0.0apps/google-contacts/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-contacts/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-docs/package.json
npmzod^4.0.0apps/google-docs/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-docs/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-sheets/package.json
npmzod^4.0.0apps/google-sheets/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-sheets/package.json
npm@zapier/connectors-sdk^0.4.6apps/google-tasks/package.json
npmzod^4.0.0apps/google-tasks/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/google-tasks/package.json
npm@zapier/connectors-sdk^0.4.6apps/harvest/package.json
npmzod^4.0.0apps/harvest/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/harvest/package.json
npm@zapier/connectors-sdk^0.4.6apps/heygen/package.json
npmzod^4.0.0apps/heygen/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/heygen/package.json
npm@zapier/connectors-sdk^0.4.6apps/linear/package.json
npmzod^4.0.0apps/linear/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/linear/package.json
npm@zapier/connectors-sdk^0.4.6apps/microsoft-onedrive/package.json
npmzod^4.0.0apps/microsoft-onedrive/package.json
npm@modelcontextprotocol/sdk^1.0.0apps/microsoft-onedrive/package.json
All dependencies 6

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk^1.0.0direct
npm@zapier/connectors-sdk^0.4.6direct
npmzod^4.0.0direct
npmtsup8.5.1indirect
npmtypescript5.9.3indirect
npmvitest4.1.11indirect
Dependency advisories 0

Installing npm:@zapier/clay-connector@0.0.6 pulls in 97 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

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