Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 06:31 UTC

mrkmg / node-external-editor

Edit a string with the users preferred text editor using $VISUAL or $EDITOR

JavaScript · TypeScriptMIT★ 44 stars⑂ 13 forkssince Jun 2016View on GitHub ↗

mrkmg/node-external-editor holds a health index of 20 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (57/100) and lowest on Vitality (18/100). It was last updated 1553 days ago. A single contributor accounts for most of its recent work.

20
overall / 100
At Risk

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.

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

Ownership

KevinPersonal account
29 followers94 public repossince Sep 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmexternal-editor3.1.087,008,859182661 days agoeditorexternaluservisual

Metrics by category

Vitality

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

18Critical · 21% of overall
How it's scored
0/36Push recency — last push 1,553 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.97
days_since_last_push1,553
active_weeks_last_year0
How it's scored
27/27Ships releases — 3 releases published
0/36Release recency — latest release 3,088 days ago
12.6/27Release cadence — a release every ~278.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tag3.0.0
releases_from_tagsno
days_since_latest_release3,088
mean_days_between_releases278.1
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
26.5/60Stars — 44 stars
9/25Forks — 13 forks
0/15Watchers — 1 watchers
Inputs used
forks13
stars44
watchers1
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 87,008,859 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesexternal-editor
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads87,008,859
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?

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11.2/22.5Commit distribution — top contributor authored 50% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.5
How it's scored
30.3/42Issue resolution — 72% of issues closed
20/30PR acceptance — 6/9 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/29 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues5
closed_issues13
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.722
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.6/25Owner reach — 29 followers of mrkmg
25/25Track record — 94 public repos, account ~16 yr old
Inputs used
followers29
owner_typeUser
is_verified—
owner_loginmrkmg
public_repos94
account_age_days5,880
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 2,661 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesexternal-editor
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,661

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configno
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?

27At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/29 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Vulnerabilities — 27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate1.6
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: tmp 0.0.33 (high 7.5)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 440 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages5
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:external-editor@3.1.0 runtime dependency closure — what installing the published package pulls in — 5 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6/40Legible commit history — 11 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.113
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.03
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes — 0/18 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes7,018
source_files_sampled18
oversized_source_files0

Key facts

44GitHub stars
3contributors
0commits, last 12 months
1,553days since last push
3releases
1bus factor
5open 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 ★ / 13 ⇿
0Stars
13Forks
2Releases

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.

03581013151312017-052021-122026-07
Major 1Minor 1Patch 0

Each point covers 9 days.

OpenSSF Scorecard 1.6 / 10
1.6aggregate

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-10-21 06:31 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 1 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 1/29 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmchardet^0.7.0package.json
npmiconv-lite^0.4.24package.json
npmtmp^0.0.33package.json
All dependencies 70

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

RegistryPackageVersionRelation
npmchardet0.7.0direct
npmiconv-lite0.4.24direct
npmtmp0.0.33direct
npm@babel/code-frame7.0.0indirect
npm@babel/highlight7.5.0indirect
npm@types/chai4.1.7indirect
npm@types/chardet0.5.0indirect
npm@types/mocha5.2.7indirect
npm@types/node10.14.12indirect
npm@types/tmp0.0.33indirect
npmansi-styles3.2.1indirect
npmargparse1.0.10indirect
npmarrify1.0.1indirect
npmassertion-error1.1.0indirect
npmbalanced-match1.0.0indirect
npmbrace-expansion1.1.11indirect
npmbrowser-stdout1.3.1indirect
npmbuffer-from1.1.1indirect
npmbuiltin-modules1.1.1indirect
npmchai4.2.0indirect
npmchalk2.4.2indirect
npmcheck-error1.0.2indirect
npmcolor-convert1.9.3indirect
npmcolor-name1.1.3indirect
npmcommander2.15.1indirect
npmconcat-map0.0.1indirect
npmdebug3.1.0indirect
npmdeep-eql3.0.1indirect
npmdiff3.5.0indirect
npmes6-shim0.35.5indirect
npmescape-string-regexp1.0.5indirect
npmesprima4.0.1indirect
npmesutils2.0.2indirect
npmfs.realpath1.0.0indirect
npmget-func-name2.0.0indirect
npmglob7.1.2indirect
npmgrowl1.10.5indirect
npmhas-flag3.0.0indirect
npmhe1.1.1indirect
npminflight1.0.6indirect
npminherits2.0.3indirect
npmjs-tokens4.0.0indirect
npmjs-yaml3.13.1indirect
npmmake-error1.3.5indirect
npmminimatch3.0.4indirect
npmminimist0.0.8indirect
npmminimist1.2.0indirect
npmmkdirp0.5.1indirect
npmmocha5.2.0indirect
npmms2.0.0indirect
npmonce1.4.0indirect
npmos-tmpdir1.0.2indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.6indirect
npmpathval1.1.0indirect
npmresolve1.11.1indirect
npmsafer-buffer2.1.2indirect
npmsemver5.7.0indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.12indirect
npmsprintf-js1.0.3indirect
npmsupports-color5.4.0indirect
npmts-node7.0.1indirect
npmtslib1.10.0indirect
npmtslint5.18.0indirect
npmtsutils2.29.0indirect
npmtype-detect4.0.8indirect
npmtypescript3.5.2indirect
npmwrappy1.0.2indirect
npmyn2.0.0indirect
Dependency advisories 1

Installing npm:external-editor@3.1.0 pulls in 5 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
tmp0.0.33directhigh20.2.6

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 statistics — npm.