Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 19:56 UTC

terkelg / prompts

❯ Lightweight, beautiful and user-friendly interactive prompts

JavaScriptMIT★ 9,309 stars⑂ 321 forkssince Feb 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

terkelg/prompts holds a health index of 32 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (79/100) and lowest on Vitality (21/100). It was last updated 447 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

TerkelPersonal account
2,043 followers53 public repossince Sep 2012

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
npmprompts2.4.2214,059,680361761 days agouipromptsclipromptinterfacecommand-lineinputcommandstdinmenuaskinteract

Metrics by category

Vitality

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

21At Risk · 21% of overall
How it's scored
0/36Push recencylast push 447 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.98
days_since_last_push447
active_weeks_last_year0
How it's scored
27/27Ships releases22 releases published
0/36Release recencylatest release 1,761 days ago
19.8/27Release cadencea release every ~115.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count22
latest_release_tagv2.4.2
releases_from_tagsno
days_since_latest_release1,761
mean_days_between_releases115.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?

79Good · 17% of overall
How it's scored
60/60Stars9,309 stars
20.9/25Forks321 forks
9.7/15Watchers57 watchers
Inputs used
forks321
stars9,309
watchers57
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads214,059,680 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesprompts
dependents
ecosystemsnpm
total_downloads
monthly_downloads214,059,680
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.3/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth61 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled61
top_contributor_share0.54
How it's scored
23/42Issue resolution55% of issues closed
22.9/30PR acceptance109/143 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 19/29 approved changesets -- score normalized to 6
Inputs used
merged_prs109
open_issues115
closed_issues139
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.547
closed_unmerged_prs34
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
23.8/25Owner reach2,043 followers of terkelg
24.6/25Track record53 public repos, account ~13 yr old
Inputs used
followers2,043
owner_typeUser
is_verified
owner_loginterkelg
public_repos53
account_age_days5,078
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 1,761 days ago
20/20Version history36 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesprompts
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,761

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows2 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 21 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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsprompt, prompts, cli, command-line, nodejs, interface, choice, prompter
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?

51Moderate · 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 21 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
4.5/7.5Code-ReviewFound 19/29 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 9 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
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
0/7.5Vulnerabilities13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Packaging, 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_packages2
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:prompts@2.4.2 runtime dependency closure — what installing the published package pulls in — 2 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.3/40Legible commit history63 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.643
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
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/39 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes8,801
source_files_sampled39
oversized_source_files0

Key facts

9,309GitHub stars
61contributors
0commits, last 12 months
447days since last push
22releases
1bus factor
115open 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 ★ / 321 ⇿
0Stars
321Forks
22Releases

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.

0125250375313402018-022022-052026-07
Major 2Minor 6Patch 14

Each point covers 8 days.

OpenSSF Scorecard 3.9 / 10
3.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-08-04 19:56 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 21 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 19/29 approved changesets -- score normalized to 6
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
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
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmkleur^4.0.1package.json
npmsisteransi^1.0.5package.json
All dependencies 95

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

RegistryPackageVersionRelation
npmkleur4.1.5direct
npmsisteransi1.0.5direct
npm@types/node18.11.17indirect
npmansi-regex2.1.1indirect
npmansi-styles2.2.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmbuffer-shims1.0.0indirect
npmcall-bind1.0.2indirect
npmchalk1.1.3indirect
npmconcat-map0.0.1indirect
npmcore-util-is1.0.3indirect
npmdeep-equal1.1.1indirect
npmdefine-properties1.1.3indirect
npmdefined1.0.0indirect
npmdotignore0.1.2indirect
npmduplexer0.1.2indirect
npmes-abstract1.19.1indirect
npmes-to-primitive1.2.1indirect
npmescape-string-regexp1.0.5indirect
npmfigures1.7.0indirect
npmfor-each0.3.3indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.1indirect
npmget-intrinsic1.1.1indirect
npmget-symbol-description1.0.0indirect
npmglob7.1.7indirect
npmhas1.0.3indirect
npmhas-ansi2.0.0indirect
npmhas-bigints1.0.1indirect
npmhas-symbols1.0.2indirect
npmhas-tostringtag1.0.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npminternal-slot1.0.3indirect
npmis-arguments1.1.1indirect
npmis-bigint1.0.4indirect
npmis-boolean-object1.1.2indirect
npmis-callable1.2.4indirect
npmis-core-module2.7.0indirect
npmis-date-object1.0.5indirect
npmis-finite1.1.0indirect
npmis-negative-zero2.0.1indirect
npmis-number-object1.0.6indirect
npmis-regex1.1.4indirect
npmis-shared-array-buffer1.0.1indirect
npmis-string1.0.7indirect
npmis-symbol1.0.4indirect
npmis-weakref1.0.1indirect
npmisarray1.0.0indirect
npmlodash4.17.21indirect
npmminimatch3.0.4indirect
npmminimist1.2.5indirect
npmobject-assign4.1.1indirect
npmobject-inspect1.11.0indirect
npmobject-is1.1.5indirect
npmobject-keys1.1.1indirect
npmobject.assign4.1.2indirect
npmonce1.4.0indirect
npmparse-ms1.0.1indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.7indirect
npmplur1.0.0indirect
npmpretty-ms2.1.0indirect
npmprocess-nextick-args1.0.7indirect
npmprocess-nextick-args2.0.1indirect
npmre-emitter1.1.3indirect
npmreadable-stream2.2.9indirect
npmreadable-stream2.3.7indirect
npmregexp.prototype.flags1.3.1indirect
npmrepeat-string1.6.1indirect
npmresolve1.20.0indirect
npmresumer0.0.0indirect
npmsafe-buffer5.1.2indirect
npmside-channel1.0.4indirect
npmsplit1.0.0indirect
npmstring.prototype.trim1.2.5indirect
npmstring.prototype.trimend1.0.4indirect
npmstring.prototype.trimstart1.0.4indirect
npmstring_decoder1.0.3indirect
npmstring_decoder1.1.1indirect
npmstrip-ansi3.0.1indirect
npmsupports-color2.0.0indirect
npmtap-out2.1.0indirect
npmtap-spec5.0.0indirect
npmtape4.14.0indirect
npmthrough2.3.8indirect
npmthrough22.0.5indirect
npmtrim0.0.1indirect
npmtypescript4.9.4indirect
npmunbox-primitive1.0.1indirect
npmutil-deprecate1.0.2indirect
npmwhich-boxed-primitive1.0.2indirect
npmwrappy1.0.2indirect
npmxtend4.0.2indirect
Dependency advisories 0

Installing npm:prompts@2.4.2 pulls in 2 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.31.0 — full methodology · metrics wiki.

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