# ExodusForks/bigint-buffer — health index 8/100 (Critical)

> Inspection of the public repository ExodusForks/bigint-buffer by inspect.software. It holds a health index of 8 out of 100, placing it in the Critical 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/ExodusForks/bigint-buffer
- Report page: https://inspect.software/software/ExodusForks/bigint-buffer
- Full JSON report: https://inspect.software/api/repositories/ExodusForks/bigint-buffer/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/e/ExodusForks/bigint-buffer.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% | 31/100 | At risk |
| Community & Adoption | 18% | 12/100 | Critical |
| Sustainability & Governance | 24% | 25/100 | Critical |
| Engineering Quality | 20% | 22/100 | Critical |
| Security | 16% | 26/100 | Critical |
| AI Readiness | not counted | 51/100 | Moderate |

A dependency reported as a malicious package applies a 35% multiplier to weighted overall health and gives it a Critical ceiling of 29.

## Repository facts

| Field | Value |
|---|---|
| Description | 💪🔢 bigint-buffer: Buffer Utilities for TC39 BigInt Proposal |
| Primary language | TypeScript |
| License | Apache-2.0 |
| Stars | 0 |
| Forks | 0 |
| Created | 2022-09-15 |
| Last push | 2026-03-15 |
| Latest release | v1.1.5-exodus.1 |
| Commits (last year) | 2 |
| Bus factor | 1 |
| Fork | yes |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | @exodus/bigint-buffer | 1.1.5-exodus.1 | 17,362 |

## Vitality — 31/100 (At risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | partial | 9.9 / 36 | last push 129 days ago |
| Commit cadence | partial | 0.7 / 36 | 1/52 weeks with commits |
| Commit volume | partial | 4.3 / 18 | 2 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 — 54/100 (Moderate)

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 | 2 version tags (no GitHub releases) |
| Release recency | partial | 27 / 36 | latest release 129 days ago |
| Release cadence | partial | 5.4 / 27 | a release every ~1276.6 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 129 days ago |

## Community & Adoption — 12/100 (Critical)

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

### Popularity & adoption — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | not met | 0 / 60 | 0 stars |
| Forks | not met | 0 / 25 | 0 forks |
| Watchers | not met | 0 / 15 | 0 watchers |

### Community health — 25/100 (Critical)

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

## Sustainability & Governance — 25/100 (Critical)

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) — 28/100 (Critical)

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

### Issue & PR responsiveness — 1/100 (Critical)

Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 46.8 | no issues or no data |
| PR acceptance | excluded | 0 / 38.2 | no decided pull requests or no data |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 46/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 2.2 / 25 | 1 followers of ExodusForks |
| Track record | partial | 14 / 25 | 207 public repos, account ~0 yr old |

## Engineering Quality — 22/100 (Critical)

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| 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 | excluded | 0 / 20 | no pull request found |

### Documentation — 10/100 (Critical)

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

## Security — 26/100 (Critical)

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 — 7/100 (Critical)

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. A dependency reported as a malicious package applies a 35% multiplier to Security posture and gives it a Critical ceiling of 29.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 0.8 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | excluded | 0 / 2.5 | no pull request found |
| 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 3 contributing companies or organizations -- score normalized to 10 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| 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 | excluded | 0 / 5 | no dependencies found |
| SAST | not met | 0 / 5 | no SAST tool detected |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | not met | 0 / 7.5 | 151 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 786 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 — 35/100 (At risk)

1 resolved dependency(ies) resolve to a version the registry still serves and the OpenSSF corpus reports as malicious. Direct and indirect are treated alike: an install-time payload runs at any depth in the graph. A report here concerns the package as published, not the maintainers of this repository, which may have resolved it unknowingly.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | partial | 35 / 100 | 1 reported as malicious: fsevents 1.2.4 |

### High-Risk Jurisdiction Exposure — 75/100 (Good)

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 | partial | 75 / 100 | Russia: contributor_organization (1) |

## AI Readiness — 51/100 (Moderate)

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 — 18/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 | 17.8 / 40 | 14 of 42 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 57/100 (Moderate)

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

| 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 47 |
| Automated maintenance | met | 8 / 8 | 5 of the last 47 commits are automated dependency updates |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

### 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/6 source files over 60KB |

## Collection warnings

- Community profile unavailable
- npm package '@exodus/bigint-buffer' points at a different repository (https://github.com/exodusMovement/bigint-buffer); excluded from ecosystem scoring
- Advisory severity resolved for 120 of 153 advisories (lookup cap); the remainder are reported as unknown severity

## 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