networkoptix/nx_open

0

/ 100

Documentation82
Engineering80
Health100
C++801d ago
Grade a repo

Solid foundation. Invest in docs and CI to grow from here.

NetworkOptix open-source components used to build Powered-by-Nx products including Desktop Client for Network Optix Video Management Platform.

Documentation

82

README12pt70

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

80

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Tests18pt80

Test files detected (artifacts/coturn/src/docker/coturn/tests).

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt100

CI is configured (artifacts/googletest/.travis.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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)
  • 33
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 2d 17h
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files24 root entries
  • artifacts
    Good: A license file is present.
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Test files detected (artifacts/coturn/src/docker/coturn/tests).
    Good: CI is configured (artifacts/googletest/.travis.yml).
    Good: Environment pinned via artifacts/coturn/src/docker/coturn/alpine/Dockerfile.
    Good: Issue or PR templates present.
    Good: Security policy present.
  • build_utils
  • cloud
  • cmake
  • conan_config
  • conan_profiles
  • dependencies
  • libs
  • licenses
  • vms
  • .gitignore
    Good: .gitignore present.
  • build_info.json.in
  • build_info.txt.in
  • build.bat
  • build.md
  • build.sh
  • CMakeLists.txt
  • CMakeSettings.json.in
  • conanfile.py
  • cpp_coding_style.md
  • launch.vs.json.in
  • nx_log_viewer.html
  • 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.
    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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).