0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Common Modules used by other XWiki top level projects
Documentation
63
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README documents how to install the project.
README is present.
Licensed under LGPL-2.1.
Engineering
68
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/backport.yml).
Test files detected (xwiki-commons-core/xwiki-commons-blame/xwiki-commons-blame-api/src/test).
Java/Kotlin linting configured (xwiki-commons-tools/xwiki-commons-tool-verification-resources/src/main/resources/checkstyle.xml).
Issue or PR templates present.
Project health
100
Dependency manifest found (pom.xml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 147Forks
- 74Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 98Watchers
Responsiveness
- -Median issue response
- 8hMedian PR merge time
- 42Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/backport.yml).Good: Issue or PR templates present.
- .mvn
- xwiki-commons-coreGood: Test files detected (xwiki-commons-core/xwiki-commons-blame/xwiki-commons-blame-api/src/test).
- xwiki-commons-pom
- xwiki-commons-toolsGood: Java/Kotlin linting configured (xwiki-commons-tools/xwiki-commons-tool-verification-resources/src/main/resources/checkstyle.xml).
- .backportrc.json
- .gitattributes
- .gitignoreGood: .gitignore present.
- .lgtm.yml
- Jenkinsfile
- LICENSEGood: Licensed under LGPL-2.1.
- pom.xmlGood: Dependency manifest found (pom.xml).
- README.mdGood: 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- SECURITY.mdGood: Security policy present.