A well-known project done right. Strong docs and solid engineering throughout.

opkssh (OpenPubkey SSH)

Documentation

92

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

85

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt75

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (commands/add_test.go).

CI/CD14pt100

CI is configured (.github/workflows/build.yml).

Linting and formatting5pt100

Formatting enforced (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 102
    Forks
  • 18
    Releaseslatest 1y ago

Community

  • Community health
  • authors own >50% of commits
  • 1,957
    Watchers

Responsiveness

  • 4h
    Median issue response
  • <1h
    Median PR merge time
  • 75
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • commands
    Good: Test files detected (commands/add_test.go).
  • docs
  • hack
  • internal
  • policy
  • scripts
  • sshcert
  • test
  • .editorconfig
    Good: Formatting enforced (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
  • .goreleaser.yaml
  • CODE-OF-CONDUCT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • logpath_unix.go
  • logpath_windows.go
  • main_test.go
  • main.go
  • opkssh.te
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • renovate.json
  • SECURITY.md
    Good: Security policy present.