# tapjs/signal-exit — health index 40/100 (At risk)

> Inspection of the public repository tapjs/signal-exit by inspect.software. It holds a health index of 40 out of 100, placing it in the At risk band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/tapjs/signal-exit
- Report page: https://inspect.software/software/tapjs/signal-exit
- Full JSON report: https://inspect.software/api/repositories/tapjs/signal-exit/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/t/tapjs/signal-exit.svg
- Inspected: 2026-07-22
- Methodology: metrics 1.13.0, report schema 0.26.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 17/100 | Critical |
| Community & Adoption | 18% | 76/100 | Good |
| Sustainability & Governance | 24% | 55/100 | Moderate |
| Engineering Quality | 20% | 49/100 | At risk |
| Security | 16% | 44/100 | At risk |
| AI Readiness | not counted | 46/100 | At risk |

Abandonment Policy applies a 85% multiplier to weighted overall health.

## Repository facts

| Field | Value |
|---|---|
| Description | when you want to fire an event no matter how a process exits. |
| Primary language | TypeScript |
| License | BlueOak-1.0.0 |
| Stars | 201 |
| Forks | 27 |
| Created | 2015-05-16 |
| Last push | 2025-10-25 |
| Latest release | v4.1.0 |
| Commits (last year) | 1 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | signal-exit | 4.1.0 | 1,032,245,504 |

## Vitality — 17/100 (Critical)

Is the project alive — is code being written and are releases shipping? Weight: 22% of the overall index.

### Development activity — 7/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | partial | 3.6 / 36 | last push 269 days ago |
| Commit cadence | partial | 0.7 / 36 | 1/52 weeks with commits |
| Commit volume | partial | 2.7 / 18 | 1 commits in the last year |
| OpenSSF Scorecard: Maintained | not met | 0 / 10 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |

### Release discipline — 32/100 (At risk)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | partial | 16.2 / 27 | 22 version tags (no GitHub releases) |
| Release recency | not met | 0 / 36 | latest release 1089 days ago |
| Release cadence | partial | 12.6 / 27 | a release every ~135.5 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | partial | 85 / 100 | no human commit for 269 days; 3 unmet obligation(s): pull requests unanswered, releases stalled, Scorecard reports it unmaintained |

## Community & Adoption — 76/100 (Good)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 18% of the overall index.

### Popularity & adoption — 54/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 37.3 / 60 | 201 stars |
| Forks | partial | 11.8 / 25 | 27 forks |
| Watchers | partial | 5 / 15 | 9 watchers |

### Community health — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (BlueOak-1.0.0) |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

### Ecosystem adoption (downloads) — 100/100 (Excellent)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | met | 80 / 80 | 1,032,245,504 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 55/100 (Moderate)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% of the overall index.

### Maintainer resilience (bus factor) — 41/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 8.8 / 22.5 | top contributor authored 61% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 12 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 12 contributing companies or organizations |

### Issue & PR responsiveness — 51/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 32.5 / 46.8 | 70% of issues closed |
| PR acceptance | partial | 18.2 / 38.2 | 29/61 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 66/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 12.5 / 25 | 53 followers of tapjs |
| Track record | partial | 23.7 / 25 | 39 public repos, account ~10 yr old |

### Package maintenance — 69/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on npm |
| Publish recency | partial | 4 / 35 | latest publish 1089 days ago |
| Version history | met | 20 / 20 | 24 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 49/100 (At risk)

Are baseline engineering and documentation practices in place? Weight: 20% of the overall index.

### Engineering practices — 48/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 3 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | not met | 0 / 16 | — |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | not met | 0 / 20 | 0 out of 1 merged PRs checked by a CI test -- score normalized to 0 |

### Documentation — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | met | 10 / 10 | — |

## Security — 44/100 (At risk)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 30/100 (At risk)

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | not met | 0 / 2.5 | 0 out of 1 merged PRs checked by a CI test -- score normalized to 0 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 0/30 approved changesets -- score normalized to 0 |
| Contributors | met | 2.5 / 2.5 | project has 12 contributing companies or organizations |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | not met | 0 / 7.5 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | not met | 0 / 5 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | met | 5 / 5 | security policy file detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | not met | 0 / 7.5 | 27 existing vulnerabilities detected |

### Dependency advisories — 100/100 (Excellent)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 331 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.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

### High-Risk Jurisdiction Exposure — 100/100 (Excellent)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 46/100 (At risk)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

### Agent context & guidance — 24/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | partial | 24.5 / 40 | 46 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 43/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

### Code legibility for models — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | met | 55 / 55 | 0/36 source files over 60KB |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt