# veithly/BountyBoard — health index 31/100 (At risk)

> Inspection of the public repository veithly/BountyBoard by inspect.software. It holds a health index of 31 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/veithly/BountyBoard
- Report page: https://inspect.software/software/veithly/BountyBoard
- Full JSON report: https://inspect.software/api/repositories/veithly/BountyBoard/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/v/veithly/BountyBoard.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.23.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 5/100 | Critical |
| Community & Adoption | 18% | 44/100 | At risk |
| Sustainability & Governance | 24% | 34/100 | At risk |
| Engineering Quality | 20% | 56/100 | Moderate |
| Security | 16% | 17/100 | Critical |
| AI Readiness | not counted | 62/100 | Moderate |

## Repository facts

| Field | Value |
|---|---|
| Description | Bounty Board is a decentralized platform designed to streamline Web3 community activities. |
| Homepage | https://bountyboard-web3.vercel.app/ |
| Primary language | TypeScript |
| Stars | 904 |
| Forks | 10 |
| Created | 2024-08-05 |
| Last push | 2025-11-04 |
| Commits (last year) | 1 |
| Bus factor | 1 |

## Vitality — 5/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 259 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 — 1/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | not met | 0 / 27 | no releases published |
| Release recency | not met | 0 / 36 | no releases |
| Release cadence | not met | 0 / 27 | no releases |
| 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 | maintenance record not established from the collected data |

## Community & Adoption — 44/100 (At risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 47.9 / 60 | 904 stars |
| Forks | partial | 8 / 25 | 10 forks |
| Watchers | partial | 3.9 / 15 | 6 watchers |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | not met | 0 / 22.5 | no license file detected |
| 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 — 34/100 (At risk)

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

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

### Issue & PR responsiveness — 38/100 (At risk)

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

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

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | partial | 10 / 30 | personal (user) account |
| Verified domain | excluded | 0 / 20 | not applicable to user accounts |
| Owner reach | partial | 12.6 / 25 | 55 followers of veithly |
| Track record | met | 25 / 25 | 132 public repos, account ~12 yr old |

## Engineering Quality — 56/100 (Moderate)

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

### Engineering practices — 50/100 (Moderate)

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 | met | 16 / 16 | .eslintrc.json |
| 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 — 65/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://bountyboard-web3.vercel.app/ |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | met | 10 / 10 | — |

## Security — 17/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 — 11/100 (Critical)

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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 | 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 | not met | 0 / 2.5 | project has 0 contributing companies or organizations -- score normalized to 0 |
| 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 | not met | 0 / 2.5 | license file not 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 | 168 existing vulnerabilities detected |

### Dependency advisories — 43/100 (At risk)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 1909 resolved dependencies against OSV; 5 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). 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 | partial | 4.4 / 35 | 7 affected: next 14.2.5 (critical 9.1), next-auth 4.24.10 (high 8.2), uuid 10.0.0 (high 7.5), +4 more |
| 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 | partial | 27.9 / 40 | 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 671 days ago |

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

## AI Readiness — 62/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 — 29/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 | 29.3 / 40 | 33 of 60 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 74/100 (Good)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | contract/SVM/Cargo.toml (toolchain convention, no task runner) |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc.json |
| Static type checking | met | 11 / 11 | contract/polkadot-hardhat/tsconfig.json, eliza-add/packages/plugin-bountyboard-evm/tsconfig.json, tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 60 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

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

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

## Collection warnings

- Could not fetch crates package 'bounty-board' from its registry
- Could not fetch npm package 'polkadot-hardhat' from its registry
- Advisory severity resolved for 120 of 150 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