Well engineered for its size. A portfolio piece worth showing off.

Identus Cloud Agent

Documentation

94

Contributing guide5pt77

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

88

Tests18pt80

Test files detected (castor/src/test).

CI/CD14pt85

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (package.json).

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)
  • 34
    Forks
  • 21
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 16h
    Median issue response
  • 19h
    Median PR merge time
  • 48
    Open issues
Repository files48 root entries
  • .allstar
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 5 ecosystems (github-actions, npm, npm, docker, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • castor
    Good: Test files detected (castor/src/test).
  • cloud-agent
  • connect
  • docs
    Good: Environment pinned via docs/docker-compose.yml.
  • event-notification
  • examples
  • infrastructure
    Issue: Build artifacts or local files may be committed (infrastructure/local/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • mercury
  • pollux
  • prism-node
  • project
  • shared
  • tests
  • vdr
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .markdownlint-cli2.yaml
  • .markdownlint.yml
  • .markdownlintignore
  • .mega-linter.yml
  • .pre-commit-config.yaml
  • .protolintrc.yml
  • .sbtopts
  • .scala-steward.conf
  • .scalafix.conf
  • .scalafmt.conf
  • .shellcheckrc
  • .yamllint.yml
  • AGENTS.md
  • build.sbt
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide includes code examples.
  • DCO.md
  • DEPENDENCIES.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • logging.md
  • MAINTAINERS.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.config.mjs
  • SECURITY.md
    Good: Security policy present.
  • version.sbt