Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 19:07 UTC

postalsys / ee-client

Front end email client for EmailEngine

JavaScript · HTMLMIT★ 2 stars⑂ 0 forkssince Jul 2025View on GitHub ↗

postalsys/ee-client holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (78/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Postal SystemsOrganization
40 followers31 public repossince May 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@postalsys/ee-client1.5.03,902104 days agoemailimapclientemailenginemailwebmail

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.8/36Commit cadence4/52 weeks with commits
13.8/18Commit volume33 commits in the last year
10/10OpenSSF Scorecard: Maintained19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year33
human_commit_share
days_since_last_push0
active_weeks_last_year4

Release discipline

100Exceptional
How it's scored
27/27Ships releases4 releases published
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~4.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count4
latest_release_tagv1.5.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases4.9
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?

33At Risk · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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
47.9/80Monthly downloads3,902 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@postalsys/ee-client
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,902
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
3.3/22.5Commit distributiontop contributor authored 85% of commits
2.7/13.5Contributor breadth2 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.853
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance5/5 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/24 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.6/25Owner reach40 followers of postalsys
23/25Track record31 public repos, account ~6 yr old
Inputs used
followers40
owner_typeOrganization
is_verified
owner_loginpostalsys
public_repos31
account_age_days2,253
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 4 days ago
20/20Version history10 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@postalsys/ee-client
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
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?

61Moderate · 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-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/24 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.5Maintained19 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
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): 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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages100
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 100 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.

48Weak · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes8,445
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config.eslintrc.json
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
36.7/55Manageable file sizes1/3 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes72,388
source_files_sampled3
oversized_source_files1

Key facts

2GitHub stars
2contributors
33commits, last 12 months
0days since last push
4releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • deps.dev does not index npm:@postalsys/ee-client@1.5.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-20 19:07 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/24 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
10Maintained19 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 100

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

RegistryPackageVersionRelation
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/eslintrc2.1.4indirect
npm@eslint/js8.57.1indirect
npm@humanwhocodes/config-array0.13.0indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/object-schema2.0.3indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@ungap/structured-clone1.3.3indirect
npmacorn8.17.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.15.0indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.16indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmdoctrine3.0.0indirect
npmescape-string-regexp4.0.0indirect
npmeslint8.57.1indirect
npmeslint-scope7.2.2indirect
npmeslint-visitor-keys3.4.3indirect
npmespree9.6.1indirect
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
npmfastq1.20.1indirect
npmfile-entry-cache6.0.1indirect
npmfind-up5.0.0indirect
npmflat-cache3.2.0indirect
npmflatted3.4.2indirect
npmfs.realpath1.0.0indirect
npmglob7.2.3indirect
npmglob-parent6.0.2indirect
npmglobals13.24.0indirect
npmgraphemer1.4.0indirect
npmhas-flag4.0.0indirect
npmignore5.3.2indirect
npmimport-fresh3.3.1indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-path-inside3.0.3indirect
npmisexe2.0.0indirect
npmjs-yaml4.3.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash.merge4.6.2indirect
npmminimatch3.1.5indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmonce1.4.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmprettier3.9.5indirect
npmpunycode2.3.1indirect
npmqueue-microtask1.2.3indirect
npmresolve-from4.0.0indirect
npmreusify1.1.0indirect
npmrimraf3.0.2indirect
npmrun-parallel1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtext-table0.2.0indirect
npmtype-check0.4.0indirect
npmtype-fest0.20.2indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmwrappy1.0.2indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 100 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.16.0 — full methodology · metrics wiki.

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