Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 15:06 UTC

zone-eu / mx-connect

Establish TCP connection to a MX server

JavaScriptEUPL-1.2★ 5 stars⑂ 12 forkssince May 2018View on GitHub ↗

zone-eu/mx-connect holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (74/100) and lowest on Community & Adoption (41/100). It was last updated 29 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Zone.euOrganization
41 followers42 public repossince Jan 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmx-connect2.0.04,1663029 days agomxsmtpmtadanetlsamta-stsemaildns

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
28.8/36Push recencylast push 29 days ago
6.2/36Commit cadence9/52 weeks with commits
17.4/18Commit volume86 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_year86
human_commit_share0.92
days_since_last_push29
active_weeks_last_year9
How it's scored
27/27Ships releases10 releases published
36/36Release recencylatest release 29 days ago
19.8/27Release cadencea release every ~104.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count10
latest_release_tagv2.0.0
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases104.4
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?

41Weak · 17% of overall
How it's scored
9.8/60Stars5 stars
8.7/25Forks12 forks
2.7/15Watchers4 watchers
Inputs used
forks12
stars5
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (EUPL-1.2)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/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_templateno
How it's scored
48.3/80Monthly downloads4,166 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmx-connect
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,166
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.6/22.5Commit distributiontop contributor authored 88% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.883
How it's scored
42/42Issue resolution100% of issues closed
26.7/30PR acceptance24/27 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs24
open_issues0
closed_issues8
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio1
closed_unmerged_prs3
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 backingorganization-owned
0/20Verified domain
11.7/25Owner reach41 followers of zone-eu
23.9/25Track record42 public repos, account ~12 yr old
Inputs used
followers41
owner_typeOrganization
is_verifiedno
owner_loginzone-eu
public_repos42
account_age_days4,613

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 29 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmx-connect
ecosystemsnpm
any_deprecatedno
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
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
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

52Moderate · 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
2.5/2.5CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/14 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
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
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
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
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
9.2/25Indirect dependencies free of known advisories2 affected: nodemailer 9.0.4 (high 7.5), joi 18.2.3 (low 3.7)
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories6
affected_packages2
assessed_packages40
unassessed_packages0
affected_by_severityhigh 1, low 1
direct_affected_packages0
Matched the npm:mx-connect@2.0.0 runtime dependency closure — what installing the published package pulls in — 40 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.

68Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history88 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.957
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,481
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
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
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
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 codeJavaScript without a type-check config
55/55Manageable file sizes0/28 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes57,588
source_files_sampled28
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

5GitHub stars
4contributors
86commits, last 12 months
29days since last push
10releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 12 ⇿
0Stars
12Forks
8Releases

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.

0246810121212018-062022-062026-07
Major 0Minor 2Patch 6

Each point covers 8 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-14 15:06 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/14 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
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
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmipaddr.js2.5.0package.json
npmmailauth5.0.1package.json
npmpunycode2.3.1package.json
All dependencies 112

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

RegistryPackageVersionRelation
npmipaddr.js2.5.0direct
npmmailauth5.0.1direct
npmpunycode2.3.1direct
npm@eslint-community/eslint-utils4.10.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.5indirect
npm@eslint/config-helpers0.7.0indirect
npm@eslint/core1.2.1indirect
npm@eslint/js10.0.1indirect
npm@eslint/object-schema3.0.5indirect
npm@eslint/plugin-kit0.7.2indirect
npm@hapi/address5.1.1indirect
npm@hapi/formula3.0.2indirect
npm@hapi/hoek11.0.7indirect
npm@hapi/pinpoint2.0.1indirect
npm@hapi/tlds1.1.7indirect
npm@hapi/topo6.0.2indirect
npm@humanfs/core0.19.2indirect
npm@humanfs/node0.16.8indirect
npm@humanfs/types0.15.0indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@nodable/entities3.0.0indirect
npm@peculiar/asn1-schema2.8.0indirect
npm@peculiar/asn1-x5092.8.0indirect
npm@peculiar/asn1-x509-logotype2.8.0indirect
npm@peculiar/utils2.0.3indirect
npm@postalsys/vmc1.1.5indirect
npm@standard-schema/spec1.1.0indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.9indirect
npm@types/json-schema7.0.15indirect
npmacorn8.18.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.15.0indirect
npmanynum1.0.1indirect
npmasn1js3.0.10indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.9indirect
npmcommander15.0.0indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmencoding-japanese2.2.0indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.8.1indirect
npmeslint-config-prettier10.1.8indirect
npmeslint-scope9.1.2indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys5.0.1indirect
npmespree11.2.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfast-xml-builder1.3.1indirect
npmfast-xml-parser5.10.1indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.4.4indirect
npmglob-parent6.0.2indirect
npmglobals17.11.0indirect
npmiconv-lite0.7.3indirect
npmignore5.3.2indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-unsafe2.0.0indirect
npmisexe2.0.0indirect
npmjoi18.2.3indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlibbase641.3.0indirect
npmlibmime5.4.1indirect
npmlibqp2.1.1indirect
npmlocate-path6.0.0indirect
npmminimatch10.2.6indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmnodemailer9.0.4indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-expression-matcher1.6.2indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmprettier3.9.6indirect
npmpunycode.js2.3.1indirect
npmpvtsutils1.3.6indirect
npmpvutils1.2.0indirect
npmsafer-buffer2.1.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstrnum2.4.2indirect
npmtldts7.4.10indirect
npmtldts-core7.4.10indirect
npmtslib2.8.1indirect
npmtype-check0.4.0indirect
npmundici8.10.0indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmxml-naming0.3.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 2

Installing npm:mx-connect@2.0.0 pulls in 40 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
nodemailer9.0.4indirecthigh49.1.1
joi18.2.3indirectlow218.2.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

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.