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

Welcome to the WSO2 Identity Server source code! For info on working with the WSO2 Identity Server repository and contributing code, click the link below.

Documentation

89

Contributing guide5pt84

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

62

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.

CI/CD14pt40

CI is configured (.github/workflows/fapi-oidc-conformance-test.yml).

Reproducibility6pt70

Lockfile present (oidc-fapi-conformance-tests/resource-server/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/identity/integration/common/utils/ISIntegrationTest.java).

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)
  • 1,002
    Forks
  • 328
    Releaseslatest 10y ago

Community

  • Community health
  • authors own >50% of commits
  • 863
    Watchers

Responsiveness

  • 11d 10h
    Median issue response
  • <1h
    Median PR merge time
  • 1,627
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/fapi-oidc-conformance-test.yml).
    Good: Issue or PR templates present.
  • docs
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • etc
  • jmeter-tests
  • legal
  • modules
    Good: Test files detected (modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/identity/integration/common/utils/ISIntegrationTest.java).
    Issue: Build artifacts or local files may be committed (modules/agents/mobile-proxy-idp/iOS/WSO2 IdPProxy/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • oidc-conformance-tests
  • oidc-fapi-conformance-tests
    Good: Lockfile present (oidc-fapi-conformance-tests/resource-server/requirements.txt). Installs are reproducible.
  • product-scenarios
  • usecases
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • issue_template.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • LICENSE.txt
  • NOTICE.txt
  • 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.
    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.
  • README.txt
  • release-guidelines.md
  • release-notes.html
  • SECURITY.md
    Good: Security policy present.