koushenhai/kcloud-platform-iot

0

/ 100

Documentation56
Engineering79
Health94
Java661Apache-2.01d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

KCloud-Platform-IoT（老寇IoT云平台）是一个企业级单体架构和微服务架构的IoT云平台。采用DDD(领域驱动设计)思想，基于Spring Boot 4.1.0、Spring Cloud 2025.1.2、Spring Cloud Alibaba 2025.1.0.0 最新版本开发的云服务多租户IoT平台，家人们，点个star！拜托啦~

Documentation

56

README12pt40

README is present.

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt60

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.

License6pt100

Licensed under Apache-2.0.

Engineering

79

CI/CD14pt57

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

Tests18pt80

Test files detected (laokou-cloud/laokou-gateway/src/test).

Reproducibility6pt92

Lockfile present (archive/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Java/Kotlin linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (pom.xml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 153
    Forks
  • 31
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 1d
    Median issue response
  • <1h
    Median PR merge time
  • 13
    Open issues
Repository files44 root entries
  • .agent
  • .claude
  • .codex
  • .github
    Good: CI is configured (.github/workflows/go.yml).
    Good: Dependabot configured for maven.
    Good: Issue or PR templates present.
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/.name) (−40 pts).Fix: Remove them and add to .gitignore.
  • .kiro
  • .qoder
  • archive
    Good: Lockfile present (archive/package-lock.json). Installs are reproducible.
  • bigScreen
  • checkstyle
  • doc
  • edgeGatewayUI
  • KAudio-Video
    Good: Environment pinned via KAudio-Video/docker-compose.yml.
  • KEdge-Gateway
  • laokou-cloud
    Good: Test files detected (laokou-cloud/laokou-gateway/src/test).
  • laokou-common
  • laokou-service
  • laokou-tool
  • openspec
  • spotbugs
  • src
  • target
  • ui
  • .deepsource.toml
  • .editorconfig
    Good: Java/Kotlin linting configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .whitesource
  • CLA.adoc
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.adoc
    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.
  • index.html
  • LICENSE
    Good: Licensed under Apache-2.0.
  • LICENSE-MIT
  • lombok.config
  • NOTICE
  • OH.doc
  • PD.doc
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • PT.adoc
  • README.adoc
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • README.md
  • renovate.json
  • SECURITY.md
    Good: Security policy present.
  • TR.doc