eclipse-iceoryx/iceoryx
Grade a repo

0

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

Eclipse iceoryx™ - true zero-copy inter-process-communication

Documentation90
Engineering59
Health68
C++2,114Apache-2.0today

Documentation

90

README12pt85

README is present.

Contributing guide5pt88

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

59

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (doc/aspice_swe3_4/example/iceoryx_component/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 479
    Forks
  • 18
    Releaseslatest 4y ago

Community

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

Responsiveness

  • 4d 23h
    Median issue response
  • 2d 23h
    Median PR merge time
  • 260
    Open issues
Repository files35 root entries
  • .github
    Good: CI is configured (.github/workflows/build-test.yml).
    Good: Issue or PR templates present.
  • bazel
  • cmake
  • doc
    Good: Test files detected (doc/aspice_swe3_4/example/iceoryx_component/test).
  • iceoryx_binding_c
  • iceoryx_examples
    Good: Environment pinned via iceoryx_examples/icedocker/docker-compose.yml.
  • iceoryx_hoofs
  • iceoryx_integrationtest
  • iceoryx_meta
  • iceoryx_platform
  • iceoryx_posh
  • tools
  • .bazelignore
  • .bazelrc
  • .cirrus.yaml
  • .clang-format
  • .clang-tidy
  • .clang-tidy-diff-scans.txt
  • .codecov.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .lycheeignore
  • BUILD.bazel
  • 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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • GOVERNANCE.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • mkdocs.yml
  • MODULE.bazel
  • NOTICE.md
  • PLANNED_FEATURES.md
  • QUALITY_DECLARATION.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.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • VERSION
  • WORKSPACE.bazel
  • WORKSPACE.bzlmod