# blues/note — health index 54/100 (Moderate)

> Inspection of the public repository blues/note by inspect.software. It holds a health index of 54 out of 100, placing it in the Moderate 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/blues/note
- Report page: https://inspect.software/software/blues/note
- Full JSON report: https://inspect.software/api/repositories/blues/note/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/b/blues/note.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.17.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 57/100 | Moderate |
| Community & Adoption | 18% | 58/100 | Moderate |
| Sustainability & Governance | 24% | 65/100 | Moderate |
| Engineering Quality | 20% | 34/100 | At risk |
| Security | 16% | 51/100 | Moderate |
| AI Readiness | not counted | 45/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | Blues Wireless Notehub & Notelib Core |
| Primary language | Go |
| License | AGPL-3.0 |
| Stars | 33 |
| Forks | 4 |
| Created | 2019-10-07 |
| Last push | 2026-07-16 |
| Latest release | v1.10.0 |
| Commits (last year) | 6 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| go | github.com/blues/note | v1.10.0 | — |

## Vitality — 57/100 (Moderate)

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

### Development activity — 47/100 (At risk)

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

### Release discipline — 72/100 (Good)

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 | 45 version tags (no GitHub releases) |
| Release recency | met | 36 / 36 | latest release 4 days ago |
| Release cadence | partial | 12.6 / 27 | a release every ~227.7 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 | maintenance record not established from the collected data |

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

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

### Popularity & adoption — 34/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 24.4 / 60 | 33 stars |
| Forks | partial | 4 / 25 | 4 forks |
| Watchers | partial | 5.8 / 15 | 12 watchers |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (AGPL-3.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 | — |

## Sustainability & Governance — 65/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) — 30/100 (At risk)

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

### Issue & PR responsiveness — 74/100 (Good)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 46.8 | no issues or no data |
| PR acceptance | partial | 34.9 / 38.2 | 42/46 decided PRs merged |
| OpenSSF Scorecard: Code-Review | partial | 4.5 / 15 | Found 9/30 approved changesets -- score normalized to 3 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 13.7 / 25 | 79 followers of blues |
| Track record | met | 25 / 25 | 99 public repos, account ~8 yr old |

### Package maintenance — 100/100 (Excellent)

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

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

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

### Engineering practices — 24/100 (Critical)

| 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 | not met | 0 / 20 | 0 out of 28 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 — 51/100 (Moderate)

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 — 41/100 (At risk)

Excluded from scoring (no data or not applicable): Branch-Protection, 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 | 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 | 0 out of 28 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 | partial | 2.2 / 7.5 | Found 9/30 approved changesets -- score normalized to 3 |
| Contributors | partial | 1.5 / 2.5 | project has 2 contributing companies or organizations -- score normalized to 6 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | met | 5 / 5 | project is fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | not met | 0 / 7.5 | 1 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 | 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 | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | partial | 6.8 / 7.5 | 1 existing vulnerabilities detected |

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

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 25 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 | partial | 26.6 / 35 | 1 affected: golang.org/x/crypto v0.53.0 (unknown) |
| 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 | met | 40 / 40 | no advisory has been public longer than 90 days |

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

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| 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 | excluded | 0 / 40 | no data |

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

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, 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 | Go (statically typed) |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| 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 | Go (statically typed) |
| Manageable file sizes | partial | 53.3 / 55 | 2/65 source files over 60KB |

### Machine-readable interfaces — 40/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | met | 40 / 40 | lib/notehub.proto |
| MCP server | not met | 0 / 20 | — |
| Runnable examples | not met | 0 / 40 | — |

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