bitwarden/server

0

/ 100

Documentation84
Engineering86
Health100
C#19,229Other5d ago
Grade a repo

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Bitwarden infrastructure/backend (API, database, Docker, etc).

Documentation

84

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt80

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

86

Tests18pt80

Test files detected (bitwarden_license/test).

Reproducibility6pt80

Lockfile present (AppHost/packages.lock.json). Installs are reproducible.

CI/CD14pt85

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

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (AppHost/AppHost.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files32 root entries
  • .aspire
  • .checkmarx
  • .claude
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • .config
  • .devcontainer
    Good: Environment pinned via .devcontainer/bitwarden_common/docker-compose.yml.
  • .git-hooks
  • .github
    Good: CI is configured (.github/workflows/build_target.yml).
    Good: Issue or PR templates present.
  • .run
  • .vscode
  • AppHost
    Good: Lockfile present (AppHost/packages.lock.json). Installs are reproducible.
    Good: Dependency manifest found (AppHost/AppHost.csproj).
  • bitwarden_license
    Good: Test files detected (bitwarden_license/test).
  • dev
  • perf
  • src
  • test
  • util
  • .dockerignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • bitwarden-server.slnx
  • CONTRIBUTING.md
  • Directory.Build.props
  • global.json
  • LICENSE_AGPL.txt
  • LICENSE_BITWARDEN.txt
  • LICENSE_FAQ.md
  • LICENSE.txt
    Good: Licensed under Other.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • TRADEMARK_GUIDELINES.md