Name: RepoGrade report for allthingsazure/eshoponcontainers
Item: allthingsazure/eshoponcontainers
Rating: 63
Author: RepoGrade

allthingsazure/eshoponcontainers

Grade a repo

/ 100

GradeD

Rough and inactive. Tests, CI, and a fuller README would revive it.

Higher than 47% of 5,156 graded repos

Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET 5, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor.

Documentation76

Engineering55

Health58

0MIT4y ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (78).

See your top fixes

Now

Potential

Top fixes

Highest-impact changes first, ranked by point weight

20 to address

1
Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
2
CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
3
CI/CD14pt
Add a lint step to catch style issues automatically.
4
CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

1 checks need work

README12pt

README is present.

Contributing guide5pt

Contributing guide is detailed and thorough.

Install and run instructions9pt

README documents how to install the project.

License6pt

100

Licensed under MIT.

Engineering

3 checks need work

Linting and formatting5pt

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Issue and PR templates6pt

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.

CI/CD14pt

CI is configured (.github/workflows/basket-api.yml).

Tests18pt

Test files detected (src/BuildingBlocks/EventBus/EventBus.Tests/InMemory_SubscriptionManager_Tests.cs).

Reproducibility6pt

Lockfile present (src/Web/WebSPA/Client/package-lock.json). Installs are reproducible.

Project health

3 checks need work

Activity5pt

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt

Repository has a description.

Housekeeping3pt

.gitignore present.

Dependency manifest6pt

100

Dependency manifest found (src/ApiGateways/Mobile.Bff.Shopping/aggregator/Mobile.Shopping.HttpAggregator.csproj).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

-
Commits (30d / 90d)
0
Forks
0
Releases

Community

-
Community health
-
authors own >50% of commits
0
Watchers

Responsiveness

-
Median issue response
-
Median PR merge time
0
Open issues

Repository files14 root entries

.github
Good: CI is configured (.github/workflows/basket-api.yml).
build
deploy
Good: Environment pinned via deploy/elk/elasticsearch/Dockerfile.
img
src
Good: Test files detected (src/BuildingBlocks/EventBus/EventBus.Tests/InMemory_SubscriptionManager_Tests.cs).
Good: Lockfile present (src/Web/WebSPA/Client/package-lock.json). Installs are reproducible.
Good: Dependency manifest found (src/ApiGateways/Mobile.Bff.Shopping/aggregator/Mobile.Shopping.HttpAggregator.csproj).
Issue: Build artifacts or local files may be committed (src/.env) (−40 pts).Fix: Remove them and add to .gitignore.
.gitattributes
.gitignore
Good: .gitignore present.
branch-guide.md
CONTRIBUTING.md
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.
Good: Contributing guide explains how to run tests.
Good: Contributing guide describes the PR/review workflow.
Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
github-actions.md
LICENSE
Good: Licensed under MIT.
README-orig.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.
Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
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.
README.md
setup-azure.md

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/allthingsazure/eshoponcontainers)](https://www.repo-grade.com/report/allthingsazure/eshoponcontainers)