opcfoundation/ua-.netstandard
Grade a repo

0

/ 100

GradeB

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

Top 18% of 5,156 graded repos

OPC Unified Architecture .NET Standard

Documentation90
Engineering80
Health100
C#2,317Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

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

90

Contributing guide5pt55

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

80

Reproducibility6pt30

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (Fuzzing/Opc.Ua.Certificates.Fuzz.Tests/CertificatesTests.cs).

CI/CD14pt85

CI is configured (.github/workflows/buildandtest.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 (Applications/ConsoleLdsServer/ConsoleLdsServer.csproj).

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)
  • 1,054
    Forks
  • 95
    Releaseslatest 6y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,317
    Watchers

Responsiveness

  • 19h
    Median issue response
  • 1h
    Median PR merge time
  • 27
    Open issues
Repository files36 root entries
  • .agents
  • .azurepipelines
  • .github
    Good: CI is configured (.github/workflows/buildandtest.yml).
    Good: Dependabot covers 2 ecosystems (nuget, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • Applications
    Good: Environment pinned via Applications/ConsoleReferenceServer/Dockerfile.
    Good: Dependency manifest found (Applications/ConsoleLdsServer/ConsoleLdsServer.csproj).
  • Docs
  • Fuzzing
    Good: Test files detected (Fuzzing/Opc.Ua.Certificates.Fuzz.Tests/CertificatesTests.cs).
  • Libraries
  • nuget
  • plans
  • Stack
  • Tests
  • Tools
  • .dockerignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .whitesource
  • appveyor.yml
  • azure-pipelines-preview.yml
  • azure-pipelines.yml
  • codecov.yml
  • common.props
  • CONTRIBUTING.md
    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).
    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.
  • Directory.Build.props
  • Directory.Build.targets
  • Directory.Packages.props
  • format-report.json
  • LICENSE.txt
    Good: Licensed under Other.
  • NuGet.config
  • 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.
    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.
  • targets.props
  • UA Core Library.slnx
  • UA.slnx
  • version.json
  • version.props
RepoGrade badge preview

Add this badge to your README

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

[![RepoGrade](https://www.repo-grade.com/api/badge/opcfoundation/ua-.netstandard)](https://www.repo-grade.com/report/opcfoundation/ua-.netstandard)

More graded C# repos