Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 07:38 UTC

jamiebuilds / spawndamnit

Take care of your spawn()

JavaScriptMIT★ 87 stars⑂ 6 forkssince Jan 2018View on GitHub ↗

jamiebuilds/spawndamnit holds a health index of 21 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (44/100) and lowest on Vitality (13/100). It was last updated 665 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Jamie KylePersonal account
8,903 followers679 public repossince Aug 2011@signalapp

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
npmspawndamnitpoints to another repo — not scored3.0.114,939,3103665 days agospawnchildprocesspromiseasynccross-spawn

Metrics by category

Vitality

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

13Critical · 21% of overall
How it's scored
0/36Push recencylast push 665 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_share
days_since_last_push665
active_weeks_last_year0
How it's scored
16.2/27Ships releases3 version tags (no GitHub releases)
7.2/36Release recencylatest release 665 days ago
5.4/27Release cadencea release every ~1,247.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv3.0.1
releases_from_tagsyes
days_since_latest_release665
mean_days_between_releases1,247.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?

43Weak · 17% of overall
How it's scored
31.4/60Stars87 stars
5.8/25Forks6 forks
0/15Watchers1 watchers
Inputs used
forks6
stars87
watchers1
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

44Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.2/22.5Commit distributiontop contributor authored 90% of commits
2.7/13.5Contributor breadth2 contributors
10/10OpenSSF Scorecard: Contributorsproject has 12 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.9
How it's scored
0/42Issue resolutionno issues or no data
15/30PR acceptance1/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/10 approved changesets -- score normalized to 1
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
25/25Owner reach8,903 followers of jamiebuilds
25/25Track record679 public repos, account ~15 yr old
Inputs used
followers8,903
owner_typeUser
is_verified
owner_loginjamiebuilds
public_repos679
account_age_days5,523
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

25At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
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/10Topics7 topics
10/10Wiki
Inputs used
topicsnode, spawn, child, processes, async, promises, events
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?

35Weak · 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 1 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.8/7.5Code-ReviewFound 1/10 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 12 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update 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
0/5Pinned-Dependenciesno data
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-Permissionsno data
0/7.5Vulnerabilities18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.9
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages7
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:spawndamnit@3.0.1 runtime dependency closure — what installing the published package pulls in — 7 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.

17Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
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
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilesyarn.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/8 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes1,360
source_files_sampled8
oversized_source_files0

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'spawndamnit' points at a different repository (https://github.com/thejameskyle/spawndamnit); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
1Releases

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.

123456612019-072022-112026-02
Major 0Minor 0Patch 1

Each point covers 6 days.

OpenSSF Scorecard 1.9 / 10
1.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-09-15 07:37 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
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
1Code-ReviewFound 1/10 approved changesets -- score normalized to 1
10Contributorsproject has 12 contributing companies or organizations
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
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmcross-spawn^7.0.5package.json
npmsignal-exit^4.0.1package.json
All dependencies 184

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

RegistryPackageVersionRelation
npmcross-spawn7.0.5direct
npmsignal-exit3.0.2direct
npmsignal-exit3.0.7direct
npmsignal-exit4.1.0direct
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npmacorn8.14.0indirect
npmacorn-walk8.3.4indirect
npmaggregate-error3.1.0indirect
npmaggregate-error4.0.1indirect
npmansi-regex5.0.1indirect
npmansi-regex6.1.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmanymatch3.1.3indirect
npmargparse1.0.9indirect
npmarray-find-index1.0.2indirect
npmarray-union1.0.2indirect
npmarray-union2.1.0indirect
npmarray-uniq1.0.3indirect
npmarrgv1.0.2indirect
npmarrify1.0.1indirect
npmarrify3.0.0indirect
npmava4.3.3indirect
npmbalanced-match1.0.0indirect
npmbinary-extensions2.3.0indirect
npmblueimp-md52.19.0indirect
npmbrace-expansion1.1.8indirect
npmbraces3.0.3indirect
npmcallsites4.2.0indirect
npmcbor8.1.0indirect
npmchalk5.3.0indirect
npmchokidar3.6.0indirect
npmchunkd2.0.1indirect
npmci-info3.9.0indirect
npmci-parallel-vars1.0.1indirect
npmclean-stack2.2.0indirect
npmclean-stack4.2.0indirect
npmclean-yaml-object0.1.0indirect
npmcli-truncate3.1.0indirect
npmcliui8.0.1indirect
npmcode-excerpt4.0.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommon-path-prefix3.0.0indirect
npmconcat-map0.0.1indirect
npmconcordance5.0.4indirect
npmconvert-to-spaces2.0.1indirect
npmcrypto-random-string1.0.0indirect
npmcurrently-unhandled0.4.1indirect
npmdate-time3.1.0indirect
npmdebug4.3.7indirect
npmdel6.1.1indirect
npmdir-glob2.0.0indirect
npmdir-glob3.0.1indirect
npmeastasianwidth0.2.0indirect
npmemittery0.11.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp2.0.0indirect
npmescape-string-regexp5.0.0indirect
npmesprima4.0.0indirect
npmesutils2.0.3indirect
npmfast-diff1.3.0indirect
npmfast-glob3.3.2indirect
npmfastq1.17.1indirect
npmfigures4.0.1indirect
npmfill-range7.1.1indirect
npmfind-up6.3.0indirect
npmfixturez1.1.0indirect
npmflow-bin0.63.1indirect
npmfs-extra5.0.0indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.3indirect
npmget-caller-file2.0.5indirect
npmglob7.1.2indirect
npmglob7.2.3indirect
npmglob-parent5.1.2indirect
npmglobby11.1.0indirect
npmglobby13.2.2indirect
npmglobby7.1.1indirect
npmgraceful-fs4.1.11indirect
npmgraceful-fs4.2.11indirect
npmignore3.3.7indirect
npmignore5.3.2indirect
npmignore-by-default2.1.0indirect
npmimurmurhash0.1.4indirect
npmindent-string4.0.0indirect
npmindent-string5.0.0indirect
npminflight1.0.6indirect
npminherits2.0.3indirect
npmirregular-plurals3.5.0indirect
npmis-binary-path2.1.0indirect
npmis-error2.2.2indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-fullwidth-code-point4.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-path-cwd2.2.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-object5.0.0indirect
npmis-promise4.0.0indirect
npmis-unicode-supported1.3.0indirect
npmisexe2.0.0indirect
npmjs-string-escape1.0.1indirect
npmjs-yaml3.14.1indirect
npmjsonfile4.0.0indirect
npmload-json-file7.0.1indirect
npmlocate-path7.2.0indirect
npmlodash4.17.21indirect
npmmap-age-cleaner0.1.3indirect
npmmatcher5.0.0indirect
npmmd5-hex3.0.1indirect
npmmem9.0.2indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmmimic-fn4.0.0indirect
npmminimatch3.0.4indirect
npmminimatch3.1.2indirect
npmms2.1.3indirect
npmnofilter3.1.0indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmp-defer1.0.0indirect
npmp-event5.0.1indirect
npmp-limit4.0.0indirect
npmp-locate6.0.0indirect
npmp-map4.0.0indirect
npmp-map5.5.0indirect
npmp-timeout5.1.0indirect
npmparse-ms2.1.0indirect
npmpath-exists5.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-type3.0.0indirect
npmpath-type4.0.0indirect
npmpicomatch2.3.1indirect
npmpify3.0.0indirect
npmpkg-conf4.0.0indirect
npmplur5.1.0indirect
npmpretty-ms7.0.1indirect
npmqueue-microtask1.2.3indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmresolve-cwd3.0.0indirect
npmresolve-from5.0.0indirect
npmreusify1.0.4indirect
npmrimraf3.0.2indirect
npmrun-parallel1.2.0indirect
npmsemver7.6.3indirect
npmserialize-error7.0.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmslash1.0.0indirect
npmslash3.0.0indirect
npmslash4.0.0indirect
npmslice-ansi5.0.0indirect
npmsprintf-js1.0.3indirect
npmstack-utils2.0.6indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmsupertap3.0.1indirect
npmtemp-dir1.0.0indirect
npmtemp-dir2.0.0indirect
npmtempy0.2.1indirect
npmtime-zone1.0.0indirect
npmto-regex-range5.0.1indirect
npmtype-fest0.13.1indirect
npmunique-string1.0.0indirect
npmuniversalify0.1.1indirect
npmwell-known-symbols2.0.0indirect
npmwhich2.0.2indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmwrite-file-atomic4.0.2indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyocto-queue1.1.1indirect
Dependency advisories 0

Installing npm:spawndamnit@3.0.1 pulls in 7 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.34.0 — full methodology · metrics wiki.

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