gcpaas/dataroom
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

🔥AI对话式生成大屏、页面，采用前后端一体化解决方案，几十种炫酷图表，支持20+数据来源接入，适用于大屏、低代码、BI场景，使用简单，代码完全开源。

Documentation90
Engineering41
Health100
Vue811Apache-2.0today

Documentation

90

Contributing guide5pt52

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 Apache-2.0.

Engineering

41

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (dataRoomFront/scripts/component-config-exporter.test.mjs).

Linting and formatting5pt100

Java/Kotlin linting configured (dataRoomFront/.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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)
  • 204
    Forks
  • 3
    Releaseslatest 5d ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 811
    Watchers

Responsiveness

  • 15d 12h
    Median issue response
  • <1h
    Median PR merge time
  • 9
    Open issues
Repository files23 root entries
  • .agents
  • .codex
  • .gitee
  • .specify
    Good: Licensed under Apache-2.0.
  • dataRoomFront
    Good: Test files detected (dataRoomFront/scripts/component-config-exporter.test.mjs).
    Good: Java/Kotlin linting configured (dataRoomFront/.editorconfig).
  • dataRoomServer
  • doc
  • docs
  • openspec
  • skills
  • specs
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CHANGELOG.md
  • 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • dockerBuild.sh
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.bat
  • release.ps1
  • release.sh