Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 20:46 UTC

forwardemail / preview-email

Automatically opens your browser and iOS Simulator to preview Node.js email messages sent with Nodemailer. Made for @forwardemail and @ladjs. Cross-browser and cross-platform email testing.

JavaScript · PugMIT★ 230 stars⑂ 25 forkssince Sep 2017View on GitHub ↗

forwardemail/preview-email holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (72/100) and lowest on AI Readiness (36/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

607 followers78 public repossince Oct 2017

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?

68Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
4.2/36Commit cadence6/52 weeks with commits
11.1/18Commit volume16 commits in the last year
7/10OpenSSF Scorecard: Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year16
human_commit_share1
days_since_last_push0
active_weeks_last_year6
How it's scored
27/27Ships releases34 releases published
36/36Release recencylatest release 31 days ago
12.6/27Release cadencea release every ~129.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count34
latest_release_tagv3.3.0
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases129.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?

71Good · 17% of overall
How it's scored
38.3/60Stars230 stars
11.5/25Forks25 forks
1.7/15Watchers3 watchers
Inputs used
forks25
stars230
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.1/22.5Commit distributiontop contributor authored 46% of commits
13.5/13.5Contributor breadth13 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled13
top_contributor_share0.464
How it's scored
42/42Issue resolution100% of issues closed
12/30PR acceptance12/30 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 10/23 approved changesets -- score normalized to 4
Inputs used
merged_prs12
open_issues0
closed_issues25
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs18
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
20/25Owner reach607 followers of forwardemail
25/25Track record78 public repos, account ~8 yr old
Inputs used
followers607
owner_typeOrganization
is_verifiedyes
owner_loginforwardemail
public_repos78
account_age_days3,250

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://forwardemail.net/docs/test-preview-email-rendering-browsers-ios-simulator
10/10Repository description
10/10Topics16 topics
10/10Wiki
Inputs used
topicspreview, email, letter, opener, previewer, emails, node, pug, render, demo, test, litmus, nodemailer, templates, engine, nodejs
has_wikiyes
homepagehttps://forwardemail.net/docs/test-preview-email-rendering-browsers-ios-simulator
docs_sitehttps://forwardemail.net/docs/test-preview-email-rendering-browsers-ios-simulator
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
0/2.5CI-Tests0 out of 10 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
3/7.5Code-ReviewFound 10/23 approved changesets -- score normalized to 4
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
5.2/7.5Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
8.5/25Indirect dependencies free of known advisories2 affected: linkify-it 5.0.0 (high 7.5), nodemailer 8.0.5 (high 7.1)
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories6
affected_packages2
assessed_packages130
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the npm:preview-email@3.3.0 runtime dependency closure — what installing the published package pulls in — 130 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 instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://forwardemail.net/llms.txt)
30.9/40Legible commit history58 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://forwardemail.net/llms.txt
legible_history_share0.58
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
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-Dependenciesdependency 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_configno
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/7 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes7,317
source_files_sampled7
oversized_source_files0

Key facts

230GitHub stars
13contributors
16commits, last 12 months
0days since last push
34releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'preview-email' points at a different repository (https://github.com/forwardemail/test-preview-emails-cross-browsers-ios-simulator-nodejs-javascript); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 25 ⇿
0Stars
25Forks
33Releases

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.

05101520252522018-052022-062026-07
Major 2Minor 2Patch 29

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-08-27 20:45 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/23 approved changesets -- score normalized to 4
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
npmci-info^3.8.0package.json
npmdisplay-notification^3.0.0package.json
npmfixpack^4.0.0package.json
npmget-port5.1.1package.json
npmmailparser^3.9.14package.json
npmnodemailer^9.0.1package.json
npmopen7package.json
npmp-event4.2.0package.json
npmp-wait-for3.2.0package.json
npmpug^3.0.3package.json
All dependencies 22

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

RegistryPackageVersionRelation
npmci-info^3.8.0direct
npmdisplay-notification^3.0.0direct
npmfixpack^4.0.0direct
npmget-port5.1.1direct
npmmailparser^3.9.14direct
npmnodemailer^9.0.1direct
npmopen7direct
npmp-event4.2.0direct
npmp-wait-for3.2.0direct
npmpug^3.0.3direct
npm@commitlint/cli^19.3.0indirect
npm@commitlint/config-conventional^19.2.2indirect
npmava^5.2.0indirect
npmcross-env^7.0.3indirect
npmeslint^8.40.0indirect
npmeslint-config-xo-lass^2.0.1indirect
npmhusky8.0.3indirect
npmlint-staged^15.2.5indirect
npmnyc^15.1.0indirect
npmremark-cli11.0.0indirect
npmremark-preset-github^4.0.4indirect
npmxo^0.54.2indirect
Dependency advisories 2

Installing npm:preview-email@3.3.0 pulls in 130 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
linkify-it5.0.0indirecthigh25.0.2
nodemailer8.0.5indirecthigh49.0.1

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.