basisvr/basis

0

/ 100

Documentation89
Engineering69
Health100
C#450Other1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Basis is an open-source social framework for VR and Desktop usage.

Documentation

89

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

69

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

CI/CD14pt57

CI is configured (.github/workflows/build-docker-server.yml).

Tests18pt80

Test files detected (Basis Server/BasisRestApi.Tests/RestApiTests.cs).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Basis Server/Basis Server.sln).

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)
  • 138
    Forks
  • 8
    Releaseslatest 4d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 450
    Watchers

Responsiveness

  • 3d
    Median issue response
  • <1h
    Median PR merge time
  • 58
    Open issues
Repository files18 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/build-docker-server.yml).
    Good: Environment pinned via .github/docker/headless/linux/Dockerfile.
    Good: Issue or PR templates present.
  • Basis
    Good: Licensed under Other.
    Good: Contributing guide is detailed and thorough.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Basis Server
    Good: Test files detected (Basis Server/BasisRestApi.Tests/RestApiTests.cs).
    Good: Dependency manifest found (Basis Server/Basis Server.sln).
  • tools
  • .csharpierignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CI.md
  • CONTRIBUTING.md
  • Directory.build.props
  • ExportSourceFiles.ps1
  • LICENSE
  • PHILOSOPHY.md
  • 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.
  • STYLE.md
  • TRADEMARK.md