jagadeeshgudditi/bevel-1

0

/ 100

Documentation93
Engineering76
Health64
0Apache-2.03y ago
Grade a repo

Solid engineering. The main gap is visibility.

An automation framework for rapidly and consistently deploying production-ready DLT platforms

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

76

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

Tests18pt80

Test files detected (examples/identity-app/tests).

Reproducibility6pt80

Lockfile present (examples/supplychain-app/besu/express_nodeJS/package-lock.json). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/chaincode_test.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

64

Activity5pt5

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

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

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (examples/supplychain-app/besu/express_nodeJS/package.json).

Housekeeping3pt100

.gitignore present.

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 files20 root entries
  • .github
    Good: CI is configured (.github/workflows/chaincode_test.yml).
    Good: Issue or PR templates present.
  • automation
  • docs
  • examples
    Good: Test files detected (examples/identity-app/tests).
    Good: Lockfile present (examples/supplychain-app/besu/express_nodeJS/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (examples/supplychain-app/besu/express_nodeJS/package.json).
  • platforms
  • _travis.yml
  • .all-contributorsrc
  • .dcilintignore
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • 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.
    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.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.jdk8
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTAINERS.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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • release-notes.md
  • reset.sh
  • run.sh