# decred/politeiagui — health index 34/100 (At Risk)

> Inspection of the public repository decred/politeiagui by inspect.software. It holds a health index of 34 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/decred/politeiagui
- Report page: https://inspect.software/software/decred/politeiagui
- Full JSON report: https://inspect.software/api/repositories/decred/politeiagui/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/d/decred/politeiagui.svg
- Inspected: 2026-09-20
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 21/100 | At Risk |
| Community & Adoption | 17% | 61/100 | Moderate |
| Sustainability & Governance | 23% | 81/100 | Excellent |
| Engineering Quality | 19% | 60/100 | Moderate |
| Security | 16% | 40/100 | Weak |
| AI Readiness | 4% | 59/100 | Moderate |

The weighted overall 54 is calibrated to 56 on the published index scale (record calibration 2026-08-02). Abandonment Policy applies a 60% multiplier to weighted overall health and gives it a ceiling of 34.

## Repository facts

| Field | Value |
|---|---|
| Classification | web-ui |
| Primary language | JavaScript |
| License | ISC |
| Stars | 61 |
| Forks | 58 |
| Created | 2017-09-15 |
| Last push | 2025-09-02 |
| Latest release | v1.4.0 |
| Commits (last year) | 0 |
| Bus factor | 3 |

## Vitality — 21/100 (At Risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | not met | 0 / 36 | last push 382 days ago |
| Commit cadence | not met | 0 / 36 | 0/52 weeks with commits |
| Commit volume | not met | 0 / 18 | 0 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 — 52/100 (Moderate)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 8 releases published |
| Release recency | not met | 0 / 36 | latest release 1488 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~73.5 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | partial | 60 / 100 | no human commit for 382 days; 6 unmet obligation(s): pull requests unanswered, issues unanswered, a fixed advisory left unapplied, releases stalled, Scorecard reports it unmaintained, CI broken |

## Community & Adoption — 61/100 (Moderate)

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

### Popularity & adoption — 47/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 28.8 / 60 | 61 stars |
| Forks | partial | 14.6 / 25 | 58 forks |
| Watchers | partial | 3.9 / 15 | 6 watchers |

### Community health — 77/100 (Good)

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

## Sustainability & Governance — 81/100 (Excellent)

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

### Maintainer resilience (bus factor) — 77/100 (Good)

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

### Issue & PR responsiveness — 95/100 (Exceptional)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 40.4 / 42 | 96% of issues closed |
| PR acceptance | partial | 27.6 / 30 | 1397/1519 decided PRs merged |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | met | 15 / 15 | all changesets reviewed |

### Ownership & stewardship — 71/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 16.3 / 25 | 183 followers of decred |
| Track record | met | 25 / 25 | 89 public repos, account ~10 yr old |

## Engineering Quality — 60/100 (Moderate)

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

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

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

### Documentation — 55/100 (Moderate)

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

## Security — 40/100 (Weak)

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

Excluded from scoring (no data or not applicable): Branch-Protection, 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 | excluded | 0 / 7.5 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| CI-Tests | not met | 0 / 2.5 | 1 out of 30 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 | met | 7.5 / 7.5 | all changesets reviewed |
| 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 | met | 7.5 / 7.5 | 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 | partial | 1.5 / 5 | dependency not pinned by hash detected -- score normalized to 3 |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | not met | 0 / 5 | security policy file not 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 | 280 existing vulnerabilities detected |

### Dependency advisories — 16/100 (Critical)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 2935 resolved dependencies against OSV; 105 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 | 1.9 / 35 | 18 affected: crypto-js 3.3.0 (critical 9.1), crypto-js 4.0.0 (critical 9.1), dompurify 2.4.0 (critical 10.0), +15 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 | 10.1 / 40 | 18 advisory-carrying package(s) unaddressed past 90 days; oldest published 1060 days ago |

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

| 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 (Exceptional)

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

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 40/100 (Weak)

| 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 | met | 40 / 40 | 89 of 95 human commits state their intent (structured subject or explanatory body) |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc.js |
| Static type checking | met | 11 / 11 | plugins-structure/apps/politeia/cypress/tsconfig.json, plugins-structure/jsconfig.json |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | met | 8 / 8 | 5 of the last 100 commits are automated dependency updates |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 3 / 10 | dependency not pinned by hash detected -- score normalized to 3 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | partial | 27 / 45 | JavaScript with type-check config (plugins-structure/apps/politeia/cypress/tsconfig.json, plugins-structure/jsconfig.json) |
| Manageable file sizes | met | 55 / 55 | 0/1150 source files over 60KB |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Could not fetch npm package 'politeiagui' from its registry
- Could not fetch npm package 'teste2e' from its registry
- Resolved dependency list truncated to 3000 of 3040 packages (counts remain complete)

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